- From: Brian Birtles via GitHub <noreply@w3.org>
- Date: Fri, 10 Oct 2025 00:12:52 +0000
- To: public-css-archive@w3.org
> > Internally Firefox has an animation observer interface which is used by DevTools. > > Do you have more details about this animation observer? I’m curious about it :) The basic interface is [here](https://searchfox.org/firefox-main/source/dom/base/nsIAnimationObserver.h) and you can see some of the implementation [here](https://searchfox.org/firefox-main/rev/b30a9b734819436853abf4eba6d768037514b3f6/dom/base/nsDOMMutationObserver.cpp#347) for example. > Also: wouldn’t this animation observer be affected by this same timing incompatibility? I mean, if it were ever to became a standardized thing, then it would also need the fix detailed in the OP, no? I think the expected behavior is that if a style flush is triggered, we should already be firing `transitionrun` before the next requestAnimationFrame (which happens to be the current Firefox behavior). From a spec point of view, I think the definition in [level 2](https://drafts.csswg.org/css-transitions-2/#transition-events) is pretty clear but could benefit from a s/idle/idle or non-existent/. -- GitHub Notification of comment by birtles Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/11665#issuecomment-3387840727 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 10 October 2025 00:12:53 UTC