When using CSS Modules, LightningCSS transforms the standard CSS keyword match-element when used with view-transition-name.
Input:
.example {
view-transition-name: match-element;
}
Current output:
.example {
view-transition-name: SkZWNq_match-element;
}
Expected output:
.example {
view-transition-name: match-element;
}
It looks like the CSS Modules scoping/transformation logic currently treats match-element as a custom identifier, even though it is a reserved keyword defined by the spec: https://drafts.csswg.org/css-view-transitions/#view-transition-name-prop
When using CSS Modules, LightningCSS transforms the standard CSS keyword
match-elementwhen used withview-transition-name.Input:
Current output:
Expected output:
It looks like the CSS Modules scoping/transformation logic currently treats
match-elementas a custom identifier, even though it is a reserved keyword defined by the spec: https://drafts.csswg.org/css-view-transitions/#view-transition-name-prop