-
Notifications
You must be signed in to change notification settings - Fork 4.3k
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
Components: Enforce consistent usage of Button and ToolbarGroup components #18817
Conversation
Pushed a fix for the two things you mentioned. |
Fixed 👍 👍 |
Thanks @jasmussen, everything looks good now. You are my CSS superhero 🥇 |
e31bff8
to
e1f908c
Compare
e1f908c
to
ae766c7
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is a solid step forward, and one that will enable further enhancements through code simplification. The HTML/Preview isn't perfect, but that "toolbar tab" pattern deserves some thought separately. As such and from a design POV, this looks good to me.
Nice work here |
Description
It also extracts some changes from #17847, cc @diegohaz:
button
tag elements toButton
components for consistencyToolbar
components withToolbarGroup
in core blocksIn addition, this PR introduced ESLint change which discourages usage on
button
tag element in all production files. The only exception issave
method implementation for the block definition.How has this been tested?
npm run test-unit
npm run lint-js
Types of changes
Refactoring
Screenshots
Before
After
No visual changes 😃
Checklist: