Major issue with syntax-highlight plugin for multi-line code blocks about eleventy-plugin-syntaxhighlight

[5t3ph]

Confirmed as aXe by myself and also @bjankord

Can be temp resolved per-user by updating your Chrome extension settings for Site Access to "on click" as shown in the screenshot:

[zachleat]

Appreciate the heads up though Tanner! I wasn't able to investigate to narrow it down to a specific extension so that is helpful 👍🏻👍🏻

[zachleat]

Moved to eleventy-plugin-syntaxhighlight repo

[zachleat]

I had someone else mention this to me earlier this week but it worked fine with an incognito window, can you rule out an extension?

[Ryuno-Ki]

Perhaps you should inform @dequelabs (e.g. https://github.com/dequelabs/axe-core) about this?

I've got plenty of addons in my setup. axe is not among them, though.

[tannerdolby]

@Ryuno-Ki Closed! Thanks for your input.

[tannerdolby]

No problem Zach!

If I obtain any relevant information or details from the issue I open in axe-core, I will update you in case that info could be helpful.

[Ryuno-Ki]

Looking at https://www.11ty.dev/docs/plugins/syntaxhighlight/ I cannot confirm:

[tannerdolby]

Yep your right! It's a chrome plugin that was causing the issue. After disabling axe - Web Accessibility Testing from my chrome extensions, the code blocks are formatted correctly!

That's odd that the axe plugin could have this much destructive behavior, but I guess just as Lighthouse audits are affected by browser plugins, the syntaxhighlight is too.

[tannerdolby]

@Ryuno-Ki You must not have any browser plugins enabled. Or if you do, could you list them? I'm curious.

[tannerdolby]

Yeah, I think that would probably be best. I will submit an issue and inform @dequelabs of this.

[Ryuno-Ki]

Since you've asked:

[Ryuno-Ki]

Please close this issue, since the problem was not caused by 11ty :-)

[lonekorean]

Also confirmed, happens when I install "axe - Web Accessibility Testing".

@tannerdolby can you link the issue you opened? I can't seem to find it.

[tannerdolby]

@lonekorean This issue (#877) is the one I opened! It's now been closed since we have determined that the problematic browser plugin is aXe - Web Accessibility Testing

[lonekorean]

@tannerdolby oh sorry! I thought you had opened one in the axe-core repo: https://github.com/dequelabs/axe-core/issues

If not, maybe we should open one there? I'm happy to do it, but you have first dibs. :)

[tannerdolby]

Ah, yes. Thanks for the reminder. Here is the issue opened in dequelabs/axe-core dequelabs/axe-core/issues/2711