Make WordPress Core

Opened 4 years ago

Closed 4 years ago

Last modified 4 years ago

#46021 closed enhancement (fixed)

Timing of Ajax loading of found Plugins vs browser autocomplete

Reported by: apermo's profile apermo Owned by: sergeybiryukov's profile SergeyBiryukov
Milestone: 5.3 Priority: normal
Severity: minor Version: 5.0.3
Component: Plugins Keywords: has-patch
Focuses: ui, accessibility, administration Cc:


Setup: any recent WordPress Version, Plugins irrelevant, Mac, Chrome

On the screen: /wp-admin/plugin-install.php

The search field allows browser based autocomplete, and in my personal example I quite often search for "better search and replace". So once I typed in "better" I already see the autocomplete. But the timing for the ajax reload is so short, that moving the hand from the keys, to the arrows, pressing down and hitting return will not be enough.

Instead it loads the already found plugins (and better will not find better search replace), and voids the browser autocomplete.

What I'd expect:

a working autocomplete, so at least a longer pause, before calling the ajax search/resetting the form, or pausing the process when arrow keys/mousemovement are registered.

Possible other solution:

disable autocomplete for the plugin search field, it's worse than the solution above, but at least the not working autocomplete, would no longer confuse the UX.

Attachments (1)

46021.diff (434 bytes) - added by donmhico 4 years ago.
Increased the wait time from 500ms to 1000ms.

Download all attachments as: .zip

Change History (5)

#1 @audrasjb
4 years ago

  • Focuses accessibility added
  • Keywords needs-patch added
  • Milestone changed from Awaiting Review to 5.3

4 years ago

Increased the wait time from 500ms to 1000ms.

#2 @donmhico
4 years ago

  • Keywords has-patch added; needs-patch removed

I tested and like @apermo mentioned, it really is kind of annoying that while using the arrow keys to select from the autocomplete suggestions, it suddenly removes the selection and perform the search. It's mainly because of the set 500ms wait time.

Like @apermo suggested, it's plausible to increase the wait time to give the user appropriate amount of time to type then navigate through the autocomplete. I did several tests on different wait times and I think 1000ms is suitable.

#3 @SergeyBiryukov
4 years ago

  • Owner set to SergeyBiryukov
  • Resolution set to fixed
  • Status changed from new to closed

In 45793:

Plugins: Adjust the pause before running plugin search AJAX request on "Add Plugins" screen to allow more time for using browser's autocomplete.

Props donmhico, apermo.
Fixes #46021.

#4 @donmhico
4 years ago

#42895 was marked as a duplicate.

Note: See TracTickets for help on using tickets.