Shift key state is not obvious (even less so than before) (7.1 beta 4)
| Originator: | ben.kennedy | ||
| Number: | rdar://15863465 | Date Originated: | 20-Jan-2014 02:47 PM |
| Status: | Duplicate/15628192 | Resolved: | 22-Jan-2014 04:42 PM |
| Product: | iOS | Product Version: | 7.1 beta 4 |
| Classification: | UI/Usability | Reproducible: | Always |
Summary: The shifted vs. unshifted state of the Shift key in the iOS keyboard is not obvious at a glance. In iOS 7.0 it was somewhat visually ambiguous; in the most recent 7.1 seeds (3 and 4) it is even more ambiguous, due to a poor choice of colouring. In all cases the Shift key is rendered using a different colour scheme compared to the rest of the keyboard, providing no contextual reference for what is an active vs. inactive state. In 7.0, the unshifted state is drawn using an open black outline, consistent with other keys; the shifted state was shown in a filled grey. In 7.1, the unshifted state is drawn in a filled white, completely opposite to the other keys; the shifted state is shown as before, which bears a closer resemblance to inactive keys. The main problem is that the unshifted state in 7.1 appears bright and highlighted (filled white), giving the impression of an active (shifted) state. Steps to Reproduce: Use the white keyboard in any application. Expected Results: The Shift keys should display an image that is visually consistent with the rest of the keyboard and conveys an easily-inferred state. Actual Results: It is difficult (or impossible) to intuit at a glance whether the Shift key is pressed or not. Version: I first noticed this problem with 7.1 seed 3. It persists with seed 4. Notes: Configuration: Attachments: '7.0 unshifted.png', '7.0 shifted.png', '7.1 unshifted.png' and '7.1 shifted.png' were successfully uploaded.
Comments
Please note: Reports posted here will not necessarily be seen by Apple. All problems should be submitted at bugreport.apple.com before they are posted here. Please only post information for Radars that you have filed yourself, and please do not include Apple confidential information in your posts. Thank you!