- From: Brian Birtles via GitHub <sysbot+gh@w3.org>
- Date: Wed, 23 Jun 2021 00:44:02 +0000
- To: public-css-archive@w3.org
> Note that I'm redefining the before-change style to be the before-change _base_ style, and the same for the after-change style. The base style does not include _any_ animation/transition effects of any kind, hence the current time of existing animations is not relevant for the purposes of triggering transitions. Oh, ok, that makes sense. > But more interesting are the parts that would be affected by this change, e.g. "complex" inherited interaction between ongoing animations and transitions, [as in this example](https://jsbin.com/qenasuvilu/edit?html,output), where no browser gets it right. With this proposal, there would be no transition on `#inner` at all, since its before/after-change (base) styles are unaffected by animations on `#outer`, and therefore the before/after-change styles are equal. I think Firefox's CSS handling here is correct but there is a bug due to running background-color animations on the compositor. If you disable the `gfx.omta.background-color` pref you will see the correct result. (Quite a while ago I wrote a few tests covering some of these cases but never finished reworking the CSS transitions WPT tests enough that I could add them there: https://bug1192592.bmoattachments.org/attachment.cgi?id=8843824) -- GitHub Notification of comment by birtles Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/6398#issuecomment-866434916 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 23 June 2021 00:44:23 UTC