Proper setup with Gin theme?

Hi Damien,

I'm having trouble reproducing this problem -- is it visible when you have Claro set as your admin theme and then disappears when you switch to Gin, or is it always invisible for you? It should only be rendering on the frontend theme, so installing it in line with Gin shouldn't affect it.

Also -- do you have any Gin extras running that allow for live inline editing? If something is rendering contentEditable elements inline, Editoria11y may be preventing itself from rendering to prevent corrupting editable data. The 2.1.x branch will only render on static pages -- 2.2.x (coming soon...) will also be visible when editing content.

Usually the first step is figuring out where it went...

1. If the module thinks it is on an admin route, or the page is being viewed by an anonymous user, or the page is being viewed by a user without the "View Editoria11y checker" permission, it will not run at all.
2. If it detects a selector that prohibits running (editable content), it will not run, but it will throw a warning in the browser console: "Editoria11y is disabled because an element matched the "preventCheckingIfPresent" parameter"
3. If it renders just fine but a theme element is covering it, if you inspect the page, you should find a "ed11y-element-panel" tag as nearly the last element in the body. You can then play with the CSS and see whether something is z-indexed in front of it or overriding its opacity or something like that.

Ah, my mistake, I was expecting something to show up on the admin side.

lily.yan → made their first commit to this issue’s fork.