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 as long as Firefox or Safari change](https://github.com/web-platform-tests/wpt/issues/43574#issuecomment-1852190860), and we both have, so hopefully that Chrome change is coming). More details in https://github.com/webcompat/web-bugs/issues/136217
Bug 1878758 Comment 6 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
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](https://github.com/web-platform-tests/wpt/issues/43574#issuecomment-1852190860), so hopefully that Chrome change is coming). More details in https://github.com/webcompat/web-bugs/issues/136217