-
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
Make SiteHub available in mobile viewports: Try moving sidebar navigation context up higher #63109
Make SiteHub available in mobile viewports: Try moving sidebar navigation context up higher #63109
Conversation
Size Change: -9 B (0%) Total Size: 1.75 MB
ℹ️ View Unchanged
|
The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the If you're merging code through a pull request on GitHub, copy and paste the following into the bottom of the merge commit message.
To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook. |
Update: I was hoping this might help fix things, but it looks like the 2024-07-04.13.38.42.mp4 |
Closing this out, as I think I've found a simpler fix for the focus issue over in 4401f60 |
What?
Split out from #63060, this PR attempts to move the
SidebarNavigationContext
provider up to the layout in the site editor.Note: this PR targets
try/sitehub-mobile
instead oftrunk
to (hopefully) make it easier to see what's going on.Why?
So that we don't need to wrap the site hub in the
SidebarContent
component which was causing issues with which buttons are focused, and added unnecessary padding.I've created this as a separate PR just to see if the idea works, and to make it easier to throw away than committing to #63060.
How?
<SidebarContent>
wrapping for the site hubSidebarNavigationContext
provider up to the layout so that the context can be shared with the site hub, without requiring extra wrappingTesting Instructions
Same as for #63060
Note: when looking at this PR, you might want to look at it with whitespace removed so that the diff is easier to read: https://github.com/WordPress/gutenberg/pull/63109/files?diff=unified&w=1
Testing Instructions for Keyboard
Screenshots or screencast