[wp-trac] [WordPress Trac] #34295: "Apply" button for screen options isn't just for the per-page setting
WordPress Trac
noreply at wordpress.org
Wed Oct 14 01:37:20 UTC 2015
#34295: "Apply" button for screen options isn't just for the per-page setting
----------------------------+------------------------------
Reporter: helen | Owner:
Type: enhancement | Status: new
Priority: normal | Milestone: Awaiting Review
Component: Administration | Version:
Severity: normal | Resolution:
Keywords: | Focuses: ui
----------------------------+------------------------------
Comment (by helen):
My inclination would be to put Apply on its own line and make it a primary
button. There are, however, some issues with this:
* Some screen options don't need an Apply button at all, so pulling it out
of the per page render method and always showing it is probably not a good
solution. @afercia noted that those options that save on Ajax don't really
provide feedback about what's happened, either visually where your eyes
are focused or for screenreaders. That should be considered separately,
just wanted to note it upfront.
* Given the above about not being able to indiscriminately show the button
all the time, it's also a bit more difficult to be smart about whether
plugins need a button.
* Because of the mixed context, it could/would be confusing as to which
options save on their own and which need the Apply button. Related
weirdness: all the data gets sent in the request, just not everything is
used.
I *think* we could do something a little funky here around filtering
whether to show the button, defaulting it to off and turning it on in some
of our own render methods. Not sure what to do about the UX trickiness of
the last point, though.
--
Ticket URL: <https://core.trac.wordpress.org/ticket/34295#comment:1>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform
More information about the wp-trac
mailing list