grapesjs

Free and Open source Web Builder Framework. Next generation tool for building templates without coding

History

TowyTowy 772b9701bc fix(parser): don't drop @container/@layer at-rules on CSS parse (#5969 ) (#6788 ) fix(parser): don't drop @container/@layer at-rules on CSS parse The browser CSS parser only recognised nestable at-rules (@container, @layer, ...) when the CSSOM reported a falsy rule `type`. That happened to work in Chrome, where the legacy `CSSRule.type` is `0` for newer at-rules, but engines that expose a real numeric type (jsdom reports `17` for `CSSContainerRule`) fell through every branch and the whole rule — selectors, styles and condition — was silently discarded. Detect nestable at-rules via `getNestableAtRule` regardless of the numeric `type`. `getNestableAtRule` already matches only when the rule's `cssText` starts with the exact `@<name>`, so normal style/keyframe rules are unaffected. The parsed condition keeps the container name and its query separated by a space, so the exported CSS is valid again (e.g. `@container somename (min-width: 300px){...}`). Fixes #5969 Co-authored-by: Claude Fable 5 <noreply@anthropic.com>		2 months ago
..
e2e	refactor: init change to monorepo (#6111)	2 years ago
model	fix(parser): don't drop @container/@layer at-rules on CSS parse (#5969) (#6788)	2 months ago
view	Initial support for nested CSS rules (#6760)	4 months ago
index.ts	Initial support for nested CSS rules (#6760)	4 months ago