[wp-trac] [WordPress Trac] #26600: Search installed themes input has no submit button
WordPress Trac
noreply at wordpress.org
Tue Mar 10 16:46:13 UTC 2015
#26600: Search installed themes input has no submit button
----------------------------------+----------------------------------------
Reporter: grahamarmfield | Owner: joedolson
Type: defect (bug) | Status: reopened
Priority: high | Milestone: 4.2
Component: Themes | Version: 3.8
Severity: normal | Resolution:
Keywords: has-patch dev- | Focuses: accessibility, javascript
feedback |
----------------------------------+----------------------------------------
Comment (by afercia):
'''About translatable string:'''
yup, have considered that, some languages have also multiple plural forms
so the current string is based on the feedback and choices from other
tickets, see
https://core.trac.wordpress.org/ticket/31349#comment:8
https://core.trac.wordpress.org/ticket/15576#comment:21
By the way, this is JavaScript, not PHP so it's a bit more complicated. I
know there's #22229 but didn't have the chance to look into that. Would
suggest to keep it simple and use always the same string, after all
"Number" is singular (hopefully in all languages?).
'''Automatic page updates or only by user request:'''
We recently faced a similar issue (mostly related to 3.2.5) see #30333. In
this specific case, I'd say it's a combination of 3.2.2 and 3.2.5. For
reference: http://www.w3.org/TR/WCAG20/#consistent-behavior
3.2.2 On Input: Changing the setting of any user interface component does
not automatically cause a change of context unless the user has been
advised of the behavior before using the component. (Level A)
3.2.5 Change on Request: Changes of context are initiated only by user
request or a mechanism is available to turn off such changes. (Level AAA)
For now I would focus on "''unless the user has been advised of the
behavior before using the component''" and provide a proper description.
Definitely worth considering a dedicated option in the personal profile,
I've seen that used in other applications, though I doubt we can do
something for 4.2. Wondering also about an "in place" option, some kind of
toggle '''before''' the search input.
>> A clever solution could be something like a "typing-intent" feature
(name inspired by "hover-intent") and some help in implementing that would
be greatly appreciated :)
> Not quite sure what you mean there.
[http://cherne.net/brian/resources/jquery.hoverIntent.html jQuery
hoverIntent] is a jQuery plugin used in core that attempts to determine
the user's intent with mouse movement, borrowed the name "typing-intent"
from there. Wondering about something to detect when users intend to
actually stop entering their search term and just then fire the search.
Asked @azaozz and turns out this kind of solution is already used on the
TinyMCE "Insert/edit link" modal, when you search for internal links. See
https://core.trac.wordpress.org/browser/trunk/src/wp-
includes/js/wplink.js#L67
But for implementing that I'd really need some help :)
--
Ticket URL: <https://core.trac.wordpress.org/ticket/26600#comment:31>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform
More information about the wp-trac
mailing list