Syntax highlighting breaks Formal Syntax for CSSSyntax
See original GitHub issue<pre class="brush: css notranslate">{{CSSSyntax}}</pre>
Our syntax highlighting breaks the CSSSyntax macro. It strips the links and explanations. Easiest fix would be fixing the content as this is not highlighted anyhow.
Issue Analytics
- State:
- Created 3 years ago
- Comments:9 (9 by maintainers)
Top Results From Across the Web
CSS syntax - Cascading Style Sheets - MDN Web Docs
Each property has a set of valid values, defined by a formal grammar, as well as a semantic meaning, implemented by the browser...
Read more >Syntax Highlight Guide | Visual Studio Code Extension API
A guide to syntax highlighting. ... The tokenization of text is about breaking the text into segments and to classify each segment with...
Read more >What's wrong with this CSS code so syntax highlighting seems ...
The following CSS snippet in a Stack Overflow snippet currently seems to have broken syntax highlighting. .grid_body { display: grid; grid- ...
Read more >Syntax Highlighting — Eleventy
A pack of Eleventy plugins for PrismJS syntax highlighting. ... You are responsible for including your favorite PrismJS theme CSS and there are...
Read more >CSS Syntax - W3Schools
p is a selector in CSS (it points to the HTML element you want to style: <p>). color is a property, and red...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@fiji-flo Took care of it. He timed a mass-edit of the content with an edit of the KS macro. So now, the KS macro is responsible for doing its own
<pre>
tag.I think we can close this once we’re certain it made it to prod as expected.
At the time of writing, it’s about 1h until the Prod build builds and also at the time of writing, GitHub is having problems with Actions.
If it’s a simple matter of a bunch of search-and-replace (78 to be exact), let’s just do that in the mdn/content and never have to think about it 😃