-
Notifications
You must be signed in to change notification settings - Fork 4.2k
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
Styles Panel: Don't force it to be closed by default. #20617
Conversation
Size Change: -1 B Total Size: 865 kB
ℹ️ View Unchanged
|
This looks good. I do wonder if we should make it an option. We could combine with #20620, and provide a few different options for styles... |
I agree with @scruffian in that it would be nice to have a set of options for the styles panel. Also, changing the current behaviour for existing blocks might be confusing. |
I'm wary of making a configurable option for something this small, particularly given that I don't think the current behaviour was intended. |
@jasmussen @mapk thoughts |
Just to clarify:
If yes to both of these, I'd say ship it as it seems an obvious improvement. |
Description
#6038 originally hid the Advanced panel by default, which I agree is the correct behaviour. In #10543, which turned the Advanced panel into the Styles panel, this behaviour was retained.
Whilst working on Automattic/jetpack#14852, I found the inability to set the
initialOpen
value of the Styles panel to be a little frustrating, but on further investigation, I'm inclined to think that #10543 incorrectly retained this behaviour from the Advanced panel, and it should be changed.How has this been tested?
Tested against Automattic/jetpack#14852.
It can also be tested against Core blocks that provide styles: for example, the Quote block.
Checklist: