W3C home > Mailing lists > Public > public-css-archive@w3.org > February 2019

Re: [csswg-drafts] [css-pseudo-4] Mark unimplemented CSSPseudoElement features at-risk (#3540)

From: Brian Birtles via GitHub <sysbot+gh@w3.org>
Date: Sun, 03 Feb 2019 23:41:15 +0000
To: public-css-archive@w3.org
Message-ID: <issue_comment.created-460099971-1549237274-sysbot+gh@w3.org>
We don't have any specific plans at this point to implement any more than:
interface CSSPseudoElement {
    readonly attribute CSSOMString type;
    readonly attribute Element element;

Furthermore, for `type` we only support `::before` and `::after`. We don't implement `Element.pseudo()` either or have any specific plans to do so but it might be worth doing just to clarify the identity issues @heycam raised since they probably affect what we currently return.

(In our implementation the only way to get a `CSSPseudoElement` is to create a CSS animation / transition on a pseudo, then call `getAnimations()` and fetch the `effect.target` of the returned `CSSAnimation` or `CSSTransition`.)

GitHub Notification of comment by birtles
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/3540#issuecomment-460099971 using your GitHub account
Received on Sunday, 3 February 2019 23:41:16 UTC

This archive was generated by hypermail 2.4.0 : Tuesday, 5 July 2022 06:41:43 UTC