Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
syntax highlighting not working for @supports (scroll-snap-type) in SCSS file
See original GitHub issueDescription
This might be related to a issue i created in Microsoft/vscode#63116
Seems like the syntax for @supports (scroll-snap-type: x mandatory) isnt supported since scroll-snap-type: x mandatory is marked in red, but display: grid isnt.
Version
- GitHub Desktop: 1.6.2
- Operating system: Windows 10.0.17763.316
Issue Analytics
- State:
- Created 5 years ago
- Comments:5 (4 by maintainers)
Top Results From Across the Web
scroll-snap-type - CSS: Cascading Style Sheets | MDN
The visual viewport of this scroll container will rest on a snap point if it isn't currently scrolled. That means it snaps on...
Read more >CSS Scroll Snapping, vertical not working - Stack Overflow
The major problem in the code snippet is that the displayed scrollbar belongs to the body, where no scroll-snap properties have been defined ......
Read more >Well-controlled scrolling with CSS Scroll Snap - web.dev
The CSS Scroll Snap feature allows web developers to create well-controlled scroll experiences by declaring scroll snapping positions.
Read more >Practical CSS Scroll Snapping
CSS scroll snapping allows you to lock the viewport to certain elements or locations after a user has finished scrolling.
Read more >How to use CSS Scroll Snap - LogRocket Blog
The first one, scroll-snap-type , is applied to the parent container. It accepts two arguments: the snap direction and the snap behavior: ....
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 Free
Top 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
I was still able to see the problem syntax highlighting using Codemirror
5.44.0which is the latest version available on NPM:If you look at these two examples you’ll see the first is being correctly parsed (note the
cm-propertyCSS class attributes):Whereas the second example isn’t parsed correctly (note the
cm-errorclass attributes):The quickest way to get this resolved in Desktop would be to raise a bug report against Codemirror itself. @obendev if you have time, they have instructions for how to submit a good bug report - it shouldn’t be a browser-specific issue.
@obendev thanks for the report! We’re using Codemirror to render diffs in the app, and we have an upgrade under review in #6918 that might address this.