The serialization of transition property should follow shortest serialization principle
Categories
(Core :: CSS Parsing and Computation, defect)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox124 | --- | fixed |
People
(Reporter: boris, Assigned: boris)
References
()
Details
Attachments
(1 file)
Per https://github.com/web-platform-tests/wpt/issues/43574, we should follow the shortest serialization principle for transition shorthand.
|
Assignee | |
Comment 1•4 months ago
|
||
Per https://github.com/web-platform-tests/wpt/issues/43574, we should
follow the shortest serialization principle for transition shorthand.
|
||
Updated•4 months ago
|
Pushed by bchiou@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/edd89a13946a Follow shortest serialization principle for transition shorthand. r=zrhoffman
Created web-platform-tests PR https://github.com/web-platform-tests/wpt/pull/44430 for changes under testing/web-platform/tests
Upstream PR merged by moz-wptsync-bot
|
||
Comment 6•2 months ago
•
|
||
FWIW this seems to have caused site breakage on pages like:
https://www.pinko.com/en-us/two-tone-platform-sneakers-SS0007P001YH700403.html
In Firefox (and Safari), the site throws an Uncaught TypeError at load time:
Uncaught TypeError: t.indexOf is not a function
for: https://www.pinko.com/on/demandware.static/Sites-pinko-us-Site/-/en_US/v1714430179241/js/main.js
This is because for some reason the site is manually parsing the computed value of transition on some element, and their code doesn't gracefully handle the possibility that the transition-delay might just be missing from the serialized value, so they end up working with undefined as if it were a string.
More details in https://github.com/webcompat/web-bugs/issues/136217 .
Probably not something that we in-particular need to worry about, since all browsers are changing behavior; but for the moment this is something that works in Chrome but not in Firefox/Safari (though dbaron said he thinks Chrome folks are willing to align on this, so hopefully that Chrome change is coming).
More details in https://github.com/webcompat/web-bugs/issues/136217
Description
•