WordPress.org

Make WordPress Core

Opened 7 months ago

Closed 4 months ago

Last modified 4 months ago

#47107 closed enhancement (invalid)

Plugin Search Input Value Should Be Kept in place

Reported by: malavvasita Owned by:
Milestone: Priority: normal
Severity: normal Version: 5.1.1
Component: Plugins Keywords:
Focuses: accessibility, javascript, administration Cc:
PR Number:

Description

Is it possible to keep entered value in text box while jumping from /wp-admin/plugins.php to /wp-admin/plugin-install.php screen or vise verse.

For example,

If I am on /wp-admin/plugins.php and I have entered value as 'Akismet Anti-Spam' and then there is no installed plugin with that term.

Now I want to Install that plugin.
So I have to click on ADD NEW and then type the term again in Search Plugins... field on /wp-admin/plugins-install.php page.

Instead of that, it could be like what ever user has inputted in Search Installed Plugins... field on plugins.php file, It should be there in Search Plugins field of plugin-install.php page.

Test Environment:
WP => Version 5.1.1
OS => Ubuntu 18.04
Browser => Chrome Version 74.0.3729.108

This is a feature request. So any one is welcome to share their thought on this.

Change History (10)

#1 @malavvasita
7 months ago

  • Focuses accessibility javascript administration added

#2 @malavvasita
7 months ago

  • Type changed from feature request to enhancement

#3 @SergeyBiryukov
7 months ago

  • Component changed from General to Plugins

Previously: #13518, #16543, #26496, #29865, #35815.

Related/duplicate: #43671

This ticket was mentioned in Slack in #accessibility by afercia. View the logs.


5 months ago

#5 @afercia
5 months ago

  • Keywords reporter-feedback added; dev-feedback needs-patch removed

Thanks @malavvasita for your feature proposal. We've discussed this during today's accessibility meeting together with some members of the design team and we're not sure the proposed behavior would be good for all users. Seems it fits with just one specific user flow, while users may want to do different things when switching between the two screens.

Seems it's basically based on the assumption the only possible action is "searching".

Do you see more situations where this behavior would be useful or is it only in the "install a plugin I didn't have" flow?

#6 @williampatton
5 months ago

I do see some value in this one in the mentioned situations (and the inverse where someone installs and then goes to the plugins page afterwards).

I'm also wondering what other scenarios this would be useful for and how it would work when the intention was not for the user to install and move between these pages.

This ticket was mentioned in Slack in #accessibility by afercia. View the logs.


4 months ago

#8 @afercia
4 months ago

@malavvasita hi! When you have a chance, please see the comment above, thanks!

Do you see more situations where this behavior would be useful or is it only in the "install a plugin I didn't have" flow?

This ticket was mentioned in Slack in #accessibility by afercia. View the logs.


4 months ago

#10 @afercia
4 months ago

  • Keywords reporter-feedback removed
  • Milestone Awaiting Review deleted
  • Resolution set to invalid
  • Status changed from assigned to closed

Discussed during today's accessibility bug scrub and agreed to close this ticket, as it's not clear what other situations would benefit from the proposed change. Discussion can continue also on closed tickets!

Last edited 4 months ago by afercia (previous) (diff)
Note: See TracTickets for help on using tickets.