Skip to content
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

Bug: UI in the Gutenberg editor appears to be broken after update to WP 6.6 or greater #36

Closed
Firestorm980 opened this issue Oct 9, 2024 · 2 comments
Assignees

Comments

@Firestorm980
Copy link

Hello. We're using editoria11y on a WordPress site using the official plugin here: https://wordpress.org/plugins/editoria11y-accessibility-checker/

We've been preparing to implement the plugin on a site that started at WordPress version 6.5.5 or lower. Originally, the UI when editing a post appeared as such:
image
Note the "2 issues" button that would toggle visibility of issues that editoria11y would find during the editing process.

When updating to version 6.6 or more of WordPress, the button no longer appears:
image
This screenshot was taken with version 6.6.2, but I've confirmed this is also true for version 6.6.

We're currently using the editoria11y plugin with default settings (no changes) and the latest version as of writing 1.0.20.

In those newer versions of WordPress, there is a new control in the center of the bar:
image

So, it is possible that this update maybe changed markup or hooks to allow the editoria11y toggle to appear.

Let me know if you have further questions or need help recreating / testing. I've tested this on a vanilla install of WordPress using Local, so it should be pretty easy to test. For a post, I just made something where I knew the content would be flagged (missing alt text, missing table headings, etc.)

@itmaybejj itmaybejj self-assigned this Oct 10, 2024
@itmaybejj
Copy link
Owner

Ahh; I see the problem. A bunch of classes changed.

The width of the containers changed too, so just adding it back causes collisions. I'll need to redesign this a little.

I'll get a hotfix out this week. Longer term I'm working on a rewrite that won't require the brittle Gutenberg injections.

@itmaybejj
Copy link
Owner

itmaybejj commented Oct 10, 2024

This should work for now. Thank you for reporting this!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants