Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Screen Options missing or at least unique IDs #10511

Closed
La-Geek opened this issue Oct 11, 2018 · 1 comment
Closed

Screen Options missing or at least unique IDs #10511

La-Geek opened this issue Oct 11, 2018 · 1 comment
Labels
Backwards Compatibility Issues or PRs that impact backwards compatability [Status] Duplicate Used to indicate that a current issue matches an existing one and can be closed

Comments

@La-Geek
Copy link

La-Geek commented Oct 11, 2018

When you work with clients and they are unexperienced WordPress users, one common way is to remove unneeded items. So the client is less confused about all these new options.

We can do this with screen options and checkbox.
screen_options

But these screen options are missing. Okay, not the big deal, you think. You could write some code in functions.php to hide unnessary items, with display:none, But nope. They don't have unique CSS IDs or Classes, like the items in the sidepanel on left side do have for example.

unique_css_class

Please, either add screen options again, or implement unique CSS handles

@chrisvanpatten
Copy link
Member

Hi @La-Geek

We have a new option screen in progress over at #10215, and more discussion over in #10210.

I'd recommend you to take a look over there. It should be included in the next version of Gutenberg, version 4.1.

Because we have an existing issue open (and a solution in the works) I'll close this up and recommend you follow along over at those other issues :)

Thanks for the report!

@chrisvanpatten chrisvanpatten added Backwards Compatibility Issues or PRs that impact backwards compatability [Status] Duplicate Used to indicate that a current issue matches an existing one and can be closed labels Oct 11, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Backwards Compatibility Issues or PRs that impact backwards compatability [Status] Duplicate Used to indicate that a current issue matches an existing one and can be closed
Projects
None yet
Development

No branches or pull requests

2 participants