@starting-style not recognized

I do not understand. I feel like I am going crazy. I am trying to get information on @starting-style but the more I look the less sane I feel. I have scoured the internet on this issue, nothing. I have asked AI, nothing. I have checked CanIUse, its supported- by like EVERY browser. My code editor? DOESN'T RECOGNIZE IT. Error: Unknown at rule @starting-stylecss(unknownAtRules) There's literally a full on tutorial talking about @starting-style as ANY OTHER property in CSS. And yet VSCode is oblivious to it. https://www.w3schools.com/cssref/atrule_starting-style.php I ask ai and get back stupid unintelligent nothingburger responses: The error Unknown at rule @starting-style occurs because @starting-style is not a valid CSS or SCSS rule. Any human reports on this issue were closed. I also tried installing vscode -languageservice and css html support I mean like com'on guys! its literally in the documentation!! https://developer.mozilla.org/en-US/docs/Web/CSS/@starting-style I've seen so many videos about this feature! WHY DOESN'T IT WORK?! I know it was a relatively new feature, but its been rolled out to all browsers and everyone supports it now. 10 months ago there was few support. I do not understand why VSCode refuses to believe it exists
W3Schools offers free online tutorials, references and exercises in all the major languages of the web. Covering popular subjects like HTML, CSS, JavaScript, Python, SQL, Java, and many, many more.
MDN Web Docs
@starting-style - CSS: Cascading Style Sheets | MDN
The @starting-style CSS at-rule is used to define starting values for properties set on an element that you want to transition from when the element receives its first style update, i.e., when an element is first displayed on a previously loaded page.
6 Replies
b1mind
b1mind4mo ago
What other tooling are you using? Any build tools? Where is this output error?
TheMasterBuilder
TheMasterBuilderOP4mo ago
vue, vite an stuff. After some messing around just now, I actually did get it to work in the browser by adding a rule ignore. It let me bypass the bug this time when I used npm run dev. Usually vue would stop me but I think that was because of another linter extension idk. I am guess vue hasn't updated their language support yet since that's the main extension I'm using for their library. Which is needed in order to read a .vue file properly. Otherwise the syntax/highlighting is completely broke. Still has that annoying underline tho.
Kevin Powell
Kevin Powell4mo ago
It could be a simple VS code issue. it takes some time for their CSS syntax highlighting to catch up on new things.
b1mind
b1mind4mo ago
I would assume it has to do with Vue <style> language server, I'm using Vite too via SvelteKit and it works fine. make sure you are uptodate with your deps, otherwise ya its up to their tooling team Also make sure you have vue extension too
b1mind
b1mind4mo ago
No description

Did you find this page helpful?