- From: Daniil Sakhapov via GitHub <sysbot+gh@w3.org>
- Date: Mon, 28 Apr 2025 09:24:13 +0000
- To: public-css-archive@w3.org
@emilio Reading more carefully the [pseudo()](https://drafts.csswg.org/css-pseudo-4/#window-interface) description: ```Return values that represent the same pseudo-element on the same originating element must be, insofar as observable, always the same CSSPseudoElement object. (The UA may drop or regenerate the object for convenience or performance if this is not observable.)``` Since we should return the same CSSPseudoElement, even when no pseudo element is created on ultimate originating element per CSS rules, I assume we just set that CSSPseudoElement's `element` and `parent` on creation and cache it? So, even when actual pseudo element is removed, this CSSPseudoElement still gives ultimate originating element for `element`. My mistake was to treat CSSPseudoElement as live actual pseudo element from a browser engine. I guess, it can be closed, unless you have any other concern about it? -- GitHub Notification of comment by danielsakhapov Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/12115#issuecomment-2834581906 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 28 April 2025 09:24:14 UTC