Repository navigation
Missing Modern CSS Support in VS Code - Maintenance concerns #53
Description
One concern with the current maintenance state of the VS Code CSS language extension is that newer CSS functionality and standards support do not appear to be implemented in a timely manner.
Because this extension is built into VS Code and effectively serves as the default CSS language experience for a huge number of developers, missing support for modern CSS features has a significant downstream impact.
Examples include newer CSS specifications and syntax additions that are already supported in browsers but still lack proper tooling support in VS Code.
The issue is less about “new features” and more about long-term standards maintenance and ecosystem reliability.
Could maintainers look into handing over the maintenance to someone more active, that take active responsibility for this repo?
This repo has effectively been abandoned by Microsoft, see:
https://github.com/microsoft/vscode-css/graphs/contributors?from=5%2F25%2F2024
Activity
[-]Maintenance issue[/-][+]Missing Modern CSS Support in VS Code - Maintenance concerns[/+]phaux commentedon May 26, 2026
Crazy how nobody noticed absolutely broken syntax highlighting in CSS for so many years. I guess everybody's CSS file is just
@import "tailwindcss"nowadays and vibe coded. I actually switched to zed for front-end projects because it's so hard to look at.thernstig commentedon Jul 20, 2026
Martin Aeschlimann (@aeschli) can you lift this internally?
romainmenke commentedon Jul 20, 2026
Patrick Brosset (@captainbrosset) This is the repo we talked about at CSSDay :)
Maybe some CSSWG folks could be given maintainer access if that is something that could help?
thernstig commentedon Aug 13, 2026
Romain Menke (@romainmenke) could you follow this up? 😃
romainmenke commentedon Aug 13, 2026
I cannot.
Given that I don't work at Microsoft I don't have any means to follow up on this outside of commenting here.
thernstig commentedon Aug 20, 2026
Alex Ross (@alexr00) ping, any ideas about this?
Example of 3 year old feature that is starting to pick up and is lacking: #19