-
Notifications
You must be signed in to change notification settings - Fork 3.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Container style queries unexpected space #4235
Comments
Maybe this is not a error the less code is correct but some text editors and Markdown renderers might automatically add a space after type and it does not affect the functionality of the code. |
@haseeb196 But it doesn't take effect in Chrome when contains a space. |
fixes issue less#4235 where container query style would have invalid space after keyword
Sorry what? AFAIK, |
@matthew-dean I don't ensure it's a function. Only |
@woody-li Ah, okay, your issue was written confusingly, because |
Sorry for my mistake, it should be |
How can I contribute to this issue? |
How to contribute to this issue? |
fixes issues less#4235 wgere container query style would have invalid space after keyword
fixes issue less#4235 where container query style would have invalid space after keyword
Any news on this? Safari 18 now supports container style queries as well, so would be nice to have this fix land in prod. Thnx! |
FWIW, you can work around this issue by escaping the @container ( ~"style(--theme: light)" ) For @container ( ~"style(--theme: @{theme})" ) (you need the extra |
@matthew-dean The release PR has merged, could you help to release new version to npm. |
To reproduce:
https://lesscss.org/less-preview/#eyJjb2RlIjoiQGNvbnRhaW5lciBzdHlsZSgtLXRoZW1lOiBkYXJrKXtcbiAgLm1haW57XG4gICAgY29sb3I6IzAwMDtcbiAgfVxufVxuXG4iLCJhY3RpdmVWZXJzaW9uIjoiNC4yLjAiLCJtYXRoIjoicGFyZW5zLWRpdmlzaW9uIiwic3RyaWN0VW5pdHMiOmZhbHNlfQ==
Current behavior:
There's a space between "style" and the bracket.
Expected behavior:
No space between "style" and the bracket.
Environment information:
less
version: 4.2.0The text was updated successfully, but these errors were encountered: