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
axe extension in chrome causing disruptive behavior for syntax highlighting with eleventy-plugin-syntaxhighlight #2711
Comments
Your welcome. I only encountered this issue while using Chrome, not sure if its reproduced in other browsers. |
I reproduced this in Microsoft Edge v87.0.664.55. Not really surprising, but another data point. |
I'm also seeing similar on Chrome when browsing datatables.net, I'd originally logged a ticket there before finding the cause was axe. |
This is also disrupting syntax highlighting by highlightjs. See the "HTML" pane at the bottom of page content here: |
Same issue as in #2686 |
Closing this issue in favor of #2686. Please continue discussion there. |
Hello dequelabs team!
This issue is in reference to Major issue with syntax-highlight plugin for multi-line code blocks within eleventy-plugin-syntaxhighlight.
I wanted to inform you that when I have the chrome extension
axe - Web Accessibility Testing
enabled, it causes disruptive behavior to eleventy-plugin-syntaxhighlight for highlighting fenced code blocks with Prism.It causes multi-line fenced code blocks to become single line and disregards the
white-space: pre
style in the Prism stylesheet. It looks like its causingwhite-space: pre
to bewhite-space: nowrap
where everything is in a single line. (Not sure if this is the exact cause but thats what it looks like)Expectation: Expect the accessibility testing extension not to cause disruptive behavior to the syntax highlighting that is handled by Prism.js within
eleventy-plugin-syntaxhighlight
.Actual: Having the
axe - Web Accessibility Testing
extension enabled with access to "all sites" causes multi-line code blocks that are highlighted witheleventy-plugin-syntaxhighlight
to have their styling messed up causing everything to be in a single line ignoring the CSS that should create line breaks.Screenshot of a multi-line code block that is forced to be single line when the accessibility extension is enabled with "site access: all sites"
Screenshot of axe extension site access details
Motivation: I want the behavior to be changed so I can continue to use the axe - Web Accessibility Testing extension alongside
eleventy-plugin-syntaxhighlight
without having to configure any non-default behavior.Currently as a workaround, @5t3ph pointed out that having the extension enabled with
site access: on click
is one way to avoid the issue I've stated above.The text was updated successfully, but these errors were encountered: