-
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
Fix site editor edit mode toggling and initial focus accessibility #69515
base: trunk
Are you sure you want to change the base?
Conversation
Size Change: +11 B (0%) Total Size: 1.84 MB
ℹ️ View Unchanged
|
This is probably obvious, but since its not mentioned in the description: With the button overlay, its not possible to scroll with mouse / touchpad / keyboard to see the full length of the preview. I can't see the whole template. |
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. |
709a75f
to
eee8ef7
Compare
In the last commit I've cleaned up things a little to preserve the scrolling. Still needs some cleaning but I won't have much time in the foreseeable future to dedicate to it. Anyone willing to take over, please do feel free to do so. |
What?
Closes #69490
Closes #59319
Closes #57400
So far, this is a PR for testing purposes. I'd appreciate feedback and thoughts from @WordPress/gutenberg-core
In the Site Editor 'view' mode, the editor canvas iframe is meant to be a preview. Clicking the whole area of the preview switches the editor to 'edit' mode. This is implemented by hacking around the
iframe
element adding arole=button
to it, a click event callback etc, It's a hack with many problems for accessibility:By using a native, transparent, button overlaid on top of the preview iframe, this PR tries a more standard approach.
Why?
How?
Uses a transparent button on top o fthe preview iframe.
So far, the button is semi-transparent for testing purposes. Ultimately, it should be fully transparent.
Testing Instructions
Edit button
.Testing Instructions for Keyboard
Screenshots or screencast