You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I pointed this at a tailwind css file with a @apply rule and the ParseStylesheet gets caught in an infinite loop in StylesheetComposer at FillDeclarations trying to handle the AtKeyword.
Thanks for posting this. While the engine shouldn't land in an endless loop, I'm not sure what to do with the rule since it's not part of the CSS2/3 standard. The @apply tag proposal was abandoned in favor of shadow parts. However some CSS pre-processors make use of it.
So the question is whether a malformed rule is something to code for. While this is fine for Tailwind, I don't know if it makes sense to try to add specific At rules as children of properties. Perhaps a generic catch-all rule would suffice - I'll have to think through this one.
I pointed this at a tailwind css file with a @apply rule and the ParseStylesheet gets caught in an infinite loop in
StylesheetComposer
atFillDeclarations
trying to handle the AtKeyword.Quick little reproduction.
As an aside, it would be pretty slick if things like this weren't ignored but included in the results.
The text was updated successfully, but these errors were encountered: