-
Notifications
You must be signed in to change notification settings - Fork 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
[ETK][GB 16.5.0] Workaround for disappearing toolbar settings button in (some) mobile viewport sizes #81050
[ETK][GB 16.5.0] Workaround for disappearing toolbar settings button in (some) mobile viewport sizes #81050
Conversation
This PR does not affect the size of JS and CSS bundles shipped to the user's browser. Generated by performance advisor bot at iscalypsofastyet.com. |
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.
Looks good and tests well for me!
This PR modifies the release build for editing-toolkit To test your changes on WordPress.com, run To deploy your changes after merging, see the documentation: PCYsg-mMA-p2 |
Proposed Changes
Make sure the settings button in the toolbar in the post editor is always visible.
The problem was introduced in this PR: WordPress/gutenberg#53412
I'm not acquainted with the rationale/specifics behind those changes, instead, I'm going to focus here on the UX issue this caused in WPCOM: the settings button can't be seen in some mobile viewport sizes and there's no alternative (that I could find) to bring it anywhere else in the UI -- this means if the user has the bad luck of reaching that specific size where the button doesn't appear, then they won't be able to bring up the settings panel at all:
Peek.2023-08-24.16-47.mp4
There's an ongoing discussion on Slack here: p1692639188443899-slack , and @draganescu created an issue for it in the GB core repo: WordPress/gutenberg#53899. There's also a WIP PR by him: WordPress/gutenberg#53908, but unfortunately, my tests were unsuccessful. Because of that, I decided to work on this temporary workaround.
Testing Instructions
apps/editing-toolkit
and runyarn dev --sync
to sync the custom ETK build to your sandbox. For the AT site, you'll need to turn it into a dev site and then sync using rsync like sowp-calypso/apps/editing-toolkit/editing-toolkit-plugin $ yarn && yarn build && rsync -azP -vvv . --exclude .git --exclude node_modules --delete <yourtestatsite>.wordpress.com@sftp.wp.com:/home/<site-id>/htdocs/wp-content/plugins/full-site-editing
Here are some screencasts of the happy paths with GB 16.5 in the post editor:
It does make the settings button sticky in the site editor -- before this change, in the site editor, the settings button would disappear in some mobile viewports, but now, due to this change, it will always be visible. I think it's a benign change and considering this is a temporary workaround, it's okay to leave it like this until a fix in core is implemented cc @draganescu[