[wp-trac] [WordPress Trac] #33704: Reduce reliance on wp_is_mobile()
WordPress Trac
noreply at wordpress.org
Fri Oct 7 15:25:10 UTC 2016
#33704: Reduce reliance on wp_is_mobile()
-------------------------+-----------------------------
Reporter: johnbillion | Owner:
Type: enhancement | Status: new
Priority: normal | Milestone: 4.7
Component: General | Version: 3.4
Severity: normal | Resolution:
Keywords: has-patch | Focuses: ui, javascript
-------------------------+-----------------------------
Comment (by akibjorklund):
@helen: The focus patch replicates current behaviour, yes. The reasoning
behind that functionality is still valid. Mobile browsers don't do well
with autofocus, because once a form element has focus, virtual keyboard
pops up and it is hard to see anything else as it consumes a big portion
of the viewport. It is useful when users knows what they are doing, but
new users have hard time scrolling around and get a feel of the whole
page/form.
I also looked into using the autofocus attribute, but the mobile browser
implementation of that is spotty. Even if it worked, it would have the
same issue mentioned above.
Autofocus is also problematic in terms of usability because it breaks the
back button (backspace, cmd+left). As such, it should only be used when
the purpose of the page is to fill in that field almost all of the time –
think front page of Google.
Also, when I have observed people filling in forms with autofocus, they
most of the time click the form element anyway to be sure there is focus –
most people can't read the subtle language of focus.
Even though as a power user I would be unhappy if the feature would go
away, I'm not sure very many people would even notice. Removal of the
whole feature could thus also be considered.
--
Ticket URL: <https://core.trac.wordpress.org/ticket/33704#comment:16>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform
More information about the wp-trac
mailing list