Re: [csswg-drafts] [cssom][css-transforms] Serializing of functions (#11556)

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

* `RESOLVED: all CSS functions seralise to lowercase`

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


-- 
GitHub Notification of comment by css-meeting-bot
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/11556#issuecomment-2842650837 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Wednesday, 30 April 2025 17:00:29 UTC