Skip to content
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

[cssom][css-transforms] Serializing of functions #11556

Open
annevk opened this issue Jan 22, 2025 · 2 comments
Open

[cssom][css-transforms] Serializing of functions #11556

annevk opened this issue Jan 22, 2025 · 2 comments

Comments

@annevk
Copy link
Member

annevk commented Jan 22, 2025

https://drafts.csswg.org/cssom/#serializing-css-values does not appear to describe how functions, such as scalex() are serialized.

I guess it should explicitly defer to https://drafts.csswg.org/css-transforms/#serialization-of-transform-functions (and other places?) but that is also very vague.

@annevk
Copy link
Member Author

annevk commented Jan 22, 2025

I think WebKit's preference would be to lowercase the function names just as we do with identifiers, but there are some tests currently that test otherwise.

@annevk annevk added the Agenda+ label Jan 22, 2025
@astearns astearns moved this to FTF agenda items in CSSWG January 2025 meeting Jan 22, 2025
@astearns astearns moved this from FTF agenda items to Regular agenda items in CSSWG January 2025 meeting Jan 22, 2025
@cdoublev
Copy link
Collaborator

cdoublev commented Jan 23, 2025

Perhaps serialization of case-insensitive identifier-like values in lowercase could be included in the general serialization principles (step 2), which are not yet included in CSSOM (#5642).

Function names are defined as case-insensitive. However, dashed function (mixin) names were defined as case-sensitive <dashed-ident> before (fe94b66). So I am not sure that all function names should serialize in lowercase.

The inconsistency between scaleX() and other CSS functions like linear-gradient(), ie. between camel and kebab case, is unfortunate. 😕

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Regular agenda items
Development

No branches or pull requests

2 participants