-
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
Site editor: do not use navigator's internal classname #56911
Site editor: do not use navigator's internal classname #56911
Conversation
…tor screens in the site editor sidebar
@@ -17,8 +20,3 @@ | |||
margin: 0 $canvas-padding; | |||
padding: $canvas-padding 0; | |||
} | |||
|
|||
.edit-site-sidebar__content > div { |
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.
I believe that NavigatorScreen
s are the only div
elements that are direct children of .edit-site-sidebar__content
, and therefore I moved those styles under the same .edit-site-sidebar__screen-wrapper
selector
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.
For now at least that's true, so I guess that's fine.
Size Change: -20 B (0%) Total Size: 1.71 MB
ℹ️ View Unchanged
|
Flaky tests detected in 86607c0. 🔍 Workflow run URL: https://github.com/WordPress/gutenberg/actions/runs/7144475382
|
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.
LGTM 👍
✅ Tests as advertised while navigating around Site Editor nav screens
✅ Relocation of nav screen padding rule makes sense, I didn't see any non-screen divs
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.
Thank you Marco!
@@ -17,8 +20,3 @@ | |||
margin: 0 $canvas-padding; | |||
padding: $canvas-padding 0; | |||
} | |||
|
|||
.edit-site-sidebar__content > div { |
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.
For now at least that's true, so I guess that's fine.
What?
Refactors the styles applied in #48822 to
NavigatorScreen
components in the site editor sidebar, so that the internal.components-navigator-screen
classname is not used.Why?
We should not use internal component's classnames, as they are not considered part of the public APIs of such components.
How?
By adding a custom classname to the
NavigatorScreen
component, and using the new classname instead of the private classname to apply the required styles.Testing Instructions
trunk
, specifically around the scrollbar styles