[cssom][css-transforms] Serializing of functions

[annevk]

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]

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.

[cdoublev]

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. 😕

[css-meeting-bot]

The CSS Working Group just discussed [cssom][css-transforms] Serializing of functions, and agreed to the following:

• RESOLVED: all CSS functions seralise to lowercase

The full IRC log of that discussion

<JoshT> TabAtkins: Lana brought up that the CSSOM spec doesn't go into detail about serealizing functions with casing
<astearns> s/Lana/anne/
<JoshT> ... the only place where this matters right now are transform functions
<JoshT> ... all others are in lower case
<JoshT> ... do we serealise transform functions in lowercase
<JoshT> ... or cannonical form>
<JoshT> ... NaN serealizes with the capital N
<emilio> q+
<weinig> q+
<JoshT> ... I suggest we do what anna says and serialise in lowercase
<astearns> ack emilio
<JoshT> ... but if compat goes the other way, I'm happy with that
<JoshT> emilio: you just addressed my comment. I think Firefox serialises with the uppercase, but I might be wrong
<JoshT> ... do we know what browsers do?
<JoshT> ... agree lowercase seems preferrable
<JoshT> astearns: there are platform tests testing for uppercase, anna says
<JoshT> keithamus: webkit would prefer lowercase
<JoshT> emilio: is their preference current behaviour
<TabAtkins> Chrome definitely serializes to uppercase currently, regardless of what you specified
<emilio> Same for Firefox
<JoshT> weinig: WebKit does capitalise
<emilio> weinig: webkit currently capitalizes
<astearns> ack weinig
<TabAtkins> q+
<JoshT> weinig: I also think we should lowercase. I don't think there is a compat issue
<JoshT> ... it parses fine and I don't think people will rely on capitalisation
<JoshT> ... seems like a weird case
<astearns> ack TabAtkins
<JoshT> TabAtkins: on the unlikely compat issues, you will only see the casing of one of these functions if ????
<TabAtkins> s/????/they query the specified style/
<JoshT> ... in matrix functions, both of these are lower case. people can't depend on casing in any case
<JoshT> emilio: that makes me more comfortable
<JoshT> ... I guess not objecting to change this
<TabAtkins> In the computed style you always see matrix() (or maybe matrix3d())
<JoshT> astearns: not hearing objections
<JoshT> ... does anyone want to argue why we'd want to muck with things when we already have tests?
<TabAtkins> we are making a change *away* from current impls tho
<JoshT> weinig: it's undefined behaviour currently. we need to make some decision
<JoshT> astearns: but this is opposite of currently implemented behaviour and tests
<JoshT> ... so proposed resolution is that all serialised functions serialise to lowercase
<JoshT> RESOLVED: all CSS functions seralise to lowercase