"Add New Person" UI Behavior Inconsistency (Error?)
When adding a new person, I have observed an inconsistency in the UI inputs. I'm going to refrain from characterizing it as a defect, as it could be either a defect or a deliberate UI choice, but either way I'm going to politely request it be reviewed.
Background: typically, pretty much anywhere on FS, when entering data into a field which has standardized formatting, I can enter e.g. "bridgeton nj" and below the entry field handy-dandy candidates for standardized values appear. I can then down-arrow to the desired candidate - "Bridgeton, Cumberland, New Jersey, United States" in this example - and hit the "Enter" key to select. Without any false modesty, I am a very, VERY fast typist, and my muscle memory with FS makes use of this behavior.
Unfortunately, I have observed a split-brain behavior in one screen which wreaks a bit of havoc with my normal data entry proficiency. I'll walk you through the scenario.
Navigate to the page of a person (any person). Now, choose one of the links to add a spouse, parent, child, whatever. The screen that pops up has input fields for the name, radio buttons for gender and living/deceased, with the last four fields being for birth date, birth location, death date, death location. With me so far?
Using only the keyboard, enter the birth date and use the arrows plus Enter key to select the desired formatted value, then move to birth location and do the same thing. Now, go to the field for death date and do the same thing (use down-arrow to highlight the desired standard-formatted value and Enter to select). Notice something? The moment you hit "Enter" to select the highlighted value the screen immediately aborts and proceeds to the next screen with only the birth date and location carried forward. This behavior is true for both the death date and death location fields, and is incongruent with every other FS interface behavior. Utilization of either of these fields when adding a new person requires that I take my hand off the keyboard and go get my mouse to make the standardized value selection. A workaround, yes, but comparatively very slow. If you suck at input you'll probably never notice, but I don't, and I do, in that order.
Is there any chance this could be reviewed as either a User Story or Defect (whichever you decide it is) for future fix?
Edit: I have committed an unforgivable sin - I didn't include my tools. 64-bit Chrome (latest version), Windows 10 Pro, x86_64 architecture. Onset of the issue: no telling. It's been like this for as long as I can remember. I kept thinking it'd get fixed, and I wasn't interested in being a pest.