Closed Devastatia closed 5 months ago
Curiously, it works as expected when Prism is replaced with highlight.js.
@Devastatia, The bug should disappear if you add language="none"
as an HTML attribute in the markup of the code-input element (or via JavaScript to the code-input element as soon as it is created).
There seems to be a problem with these lines of code:
I'm afraid I'm quite busy right now but the bug's scope being restricted to Prism suggests it might be due to Prism's functionality of adding the language-none
class, which is not part of highlight.js. I will be available shortly after 25 May and will look at this bug more then.
Clearly, if you know how to fix it, comments / a pull request are very welcome, but not required.
The language attribute is ignored regardless of what I set it to ("HTML", "html", "CSS", etc.)
code-input.language is set to "none"
pre and code classes both set to "language-none"
The attached screenshot tells all.