Pop-Up Windows (add new and all editing) and Editable Fields: Display Errors

grace316shockley

I work in FamilySearch using Google Chrome on an iPad, and I use the iPad in a horizontal orientation. Prior to the recent design changes, I never experienced any display issues when working in any editing windows or fields. Since the design changes were implemented—working in FamilySearch using the same device and methods—EVERY window that opens to allow new information to be added or edits to be made to existing information (profile creation, sources, facts, notes, etc.) fails to display all fields and information. When selecting any editable field within those windows and typing any initial letter, number, character, etc., that field and the entire window itself “shrinks,” making it impossible to view any characters being typed. 

I apologize for my clumsy description of these issues and the lack of technical terminology; I’m a historian, not an engineer. I’m attaching some screenshots in sequence in the hopes they provide a better illustrate of the problems. The first set of three images show what occurs when creating a new profile, and the second set of three images show what occurs when making edits to source citations. 

I should also mention that the above problems do not occur to the same degree if I turn my device from a horizontal orientation to a vertical one. The editing windows still do not display all fields and information within, but it is possible to view at least two lines of characters at a time when typing in a given field. I do realize it might seem like an easy “fix” to just begin using my device in the vertical orientation instead of the horizontal orientation when working in FamilySearch, but I find functionality in the horizontal orientation to be superior in every way (barring this issue). I very much hope this issue can be resolved. I have no coding experience, but it seems reasonable to hope this is fixable since there were no problems at all with the display of pop-up windows and editable fields when

using the “old” version and these issues have only begun occurring with the implementation of the new design. Thank you!

lyleblunttoronto1

Thank you for the details.