Why is there an odd behavior when typing "." after a space at the end of a word in data entry forms?

Douglas McPhaden

The exact situation just experienced is in the Reason to Detach Source field in the Detach Source window.

The behavior is: "...tion "

typing a "." as the next character yields: "tion|. " where | is the cursor

886EZLContact ID

Douglas, If I understand correctly, you are detaching a source and when you type the reason statement you are typing a word that ends in "tion" and then a period. But you are saying that the system is adding a space between the word ending and the period. Is that correct?

I just tried it in the example below and did not get the same results.

Perhaps you should clear your browser cache, cookies and history and try again. Then try using a different browser. FamilySearch supports Chrome, Safari, Firefox and Edge.

Also, it would be good for us to know if you are using a mobile device or a computer and if you are using the Family Tree mobile app or the FamilySearch.org website. Thanks!

Gordon Collett

886EZL, Douglas typed a space, then the period. You typed a period then the space.

However, in Safari on my desktop Mac, I don't have the problem occur:

This may be device dependent and no one may be able to answer or fix this without knowing your device, operating system with version, whether using the web based FamilySearch or the mobile app, what browser and version, or what app version. Even then they will only be able to track down the problem if they can replicate it. Sorry for the useless answer.

Douglas McPhaden

886EZL,

as Gordon notes you must not have read my note correctly. In addition, I am not exactly certain when this occurs. "clear your browser cache, cookies and history and try again" is not a serious recommendation in this day and age.

Gordon,

"they will only be able to track down the problem if they can replicate it" is a fairy tail. Until the PC Age bug fixers, dump busters, defect hunters, or whatever you call them (full time bug fixers), only had a replicable problem around 1 in 1000+. Yet most problems were fixed. They fixed bugs that existed in 50 thread applications, where the 23rd deadlocked with another thread, which one being a mystery. In addition bugs were fixed over the phone when the dumps contained classified information.

The Safari statement could be telling. The problem is probably in the Windows Text Editor Object used in the Community for comments .

Douglas McPhaden

I just experienced the behavior on a Community Leave a Comment box. But not this one.