Email or username:

Password:

Forgot your password?
3 comments
Bramus

UPDATE: Jake found a workaround to bypass that Chrome bug: register the custom property with @​property.

That works.

But

Safari doesn’t like it. It seems to be stuck in a transition loop when the custom props is registered to contain string values ("<string>" or "*") 😕

Bramus

Here’s something nice by @matthewp built on top of all this: a Selector Matcher Observer powered by CSSStyleObserver.

When the element matches the given selector, a custom property gets flipped, triggering the callback attached to the CSSStyleObserver.

codepen.io/bramus/pen/zYVJBje

Bramus

Yesterday I collected all bugs I could find related to `transition-behavior: allow-discrete` onto a dedicated repo/site [^1] and also filed a bunch bugs.

The WebKit team at Apple didn’t waste any time and moved really fast on this one, as the PR to fix the WebKit bugs [^2] is already merged in! 🤩👏

[^1]: allow-discrete-bugs.netlify.ap
[^2]: github.com/WebKit/WebKit/pull/

Go Up