[wp-trac] [WordPress Trac] #37230: Shiny Updates: "Installed Plugin" shiny search issues

[WordPress Trac]

#37230: Shiny Updates: "Installed Plugin" shiny search issues
-------------------------------------+-------------------------------------
 Reporter:  afercia                  |      Owner:
     Type:  defect (bug)             |     Status:  new
 Priority:  normal                   |  Milestone:  4.6
Component:  Plugins                  |    Version:  trunk
 Severity:  normal                   |   Keywords:  needs-patch shiny-
  Focuses:  ui, accessibility,       |  updates
  javascript                         |
-------------------------------------+-------------------------------------
 In the Installed Plugins screen, the search is now a "live" search,
 meaning the results will be updated live as you type.
 I'm all for improvements like this one, however I've noticed some issues.
 I'm sorry for being a bit late but to be honest I've missed the "Shiny
 Updates" was going to be also a "Shiny Search". I've quickly discussed
 this with @swissspidy at WCEU in Vienna and hopefully there's still time
 to address the main issues.

 When a functionality changes behaviour, the interface should preferably
 reflect the change to inform users that something works in a different way
 now. By the way, there are no visual UI changes or any instructions to
 inform users about this new behaviour. WordPress is already using "live"
 searches, for example in the Themes screen and in the Customizer, and the
 new Plugin search should follow the previous implementations, also for
 better consistency.

 Some points:

 1. When JavaScript is on and the live search works, the submit button
 "Search Installed Plugins" is useless and maybe even confusing for users.
 The interface should suggest users this is a "live" search. Maybe consider
 to hide the button when JS is on. When JS is off, the search works with a
 traditional page reload and needs a submit button.

 2. The "Live" search field should be visually clearly distinguished from
 "standard" search fields, this is material for designers :) wondering if
 any design feedback has been asked for the new search?

 3. For accessibility there's the need to inform users using an `aria-
 describedby` attribute on the search field, as already done for example
 for the Themes search, that points to an element with a description,
 preferably using the same text: "The search results will be updated as you
 type." By the way, when JS is off this aria-describeby attribute should
 not be used.

 4. For accessibility, there's the need to announce the number of search
 results otherwise users will experience a total lack of feedback. This
 should be done also for consistency with the Themes live search: all the
 "live" searches should work consistently across WordPress.

 5. The live search doesn't work in IE 8 and gives a JS error (IE 8 doesn't
 know what `history` is...), I guess this is the same for IE 9.

--
Ticket URL: <https://core.trac.wordpress.org/ticket/37230>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform