W3C home > Mailing lists > Public > public-css-archive@w3.org > March 2020

Re: [csswg-drafts] [web-animations-1] Clarification about `target` and `pseudoElement` relationship (#4745)

From: lpd-au via GitHub <sysbot+gh@w3.org>
Date: Tue, 10 Mar 2020 17:46:42 +0000
To: public-css-archive@w3.org
Message-ID: <issue_comment.created-597223114-1583862401-sysbot+gh@w3.org>
> The main reason for allowing unsupported pseudo-elements is to allow `target` and `pseudoElement` to be set in either order (since supported pseudo-elements can vary between elements). It is also consistent with getComputedStyle().

This makes sense to me, I guess what I really want is something like a form of `CSS.supports()` that accepts an element and a pseudo-selector, which can be called prior to creating/updating an animation.

> Doesn't checking the event's pseudoElement imply that the animation in the animation event is different than the one which was constructed (such that the pseudoElement may vary)? I would have expected it to be the same WebAnimation object.

Yes as far as I can tell by looking at Canary's implementation, the events fired are identical for `::before` and `::blargh`; that is, no animation events are fired and the `finish` animation playback events are identical.

GitHub Notification of comment by lpd-au
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/4745#issuecomment-597223114 using your GitHub account
Received on Tuesday, 10 March 2020 17:46:45 UTC

This archive was generated by hypermail 2.4.0 : Tuesday, 5 July 2022 06:42:02 UTC