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: Brian Birtles via GitHub <sysbot+gh@w3.org>
Date: Mon, 09 Mar 2020 23:59:38 +0000
To: public-css-archive@w3.org
Message-ID: <issue_comment.created-596834928-1583798377-sysbot+gh@w3.org>
> I have a question related to this. If I've followed all the rabbit holes of the spec correctly, it currently says that when an animation with a syntactically invalid `<pseudo-element-selector>` is created, a `DOMException` with error name `SyntaxError` is thrown. When I pass the pseudo-selector `::blargh` to `Element.animate()`, I receive back a valid animation object in Canary and _"TypeError: Element.animate: Unsupported pseudo-selector '::blargh'"_ in Nightly. Which implementation is correct?

The change to use a `SyntaxError` instead of a `TypeError` is a very recent one (yesterday?) so I suspect neither browser returns that yet.

However, `::blargh` is _not_ syntactically invalid so I think Nightly is wrong here.

@BorisChiou I think [bug 1610981](https://bugzilla.mozilla.org/show_bug.cgi?id=1610981) might have added some incorrect tests here. Specifically here:


It looks like the spec says we should accept invalid pseudos.

GitHub Notification of comment by birtles
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/4745#issuecomment-596834928 using your GitHub account
Received on Monday, 9 March 2020 23:59:40 UTC

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