sent https://github.com/w3ctag/design-reviews/issues/1233
вт, 26 мая 2026 г. в 20:45, Alex Russell <[email protected]>: > Hey Daniil, > > This looks like a great feature, but also feels like something I'd like > the TAG to at least be aware of in order to help drive consistency across > the platform (e.g., are there other properties that should get the same > treatment? If so, the TAG should be requesting it of the CSSWG). Can you at > least file an FYI request? > > Best, > > Alex > > On Tuesday, May 26, 2026 at 5:14:33 AM UTC-7 Chromestatus wrote: > >> *Contact emails* >> [email protected] >> >> *Explainer* >> *No information provided* >> >> *Specification* >> https://drafts.csswg.org/css-pseudo-4/#CSSPseudoElement-interface >> >> *Summary* >> Support for CSSPseudoElement - which is currently only defined for >> ::after, ::before, and ::marker - is now being extended to include several >> new pseudo-elements: ::backdrop: useful for closing a dialog when the >> backdrop is clicked, without interfering with clicks inside the dialog's >> content. This eliminates the need for complex intersection logic to >> determine where the click occurred. ::scroll-marker: can be used to collect >> click statistics. view transitions: enables geometry-aware view >> transitions.It also allows you to intercept a view transition mid-flight to >> start a new one, utilizing the coordinates of the currently animating >> element to avoid sudden visual jumps. >> >> *Blink component* >> Blink>CSS >> <https://issues.chromium.org/issues?q=customfield1222907:%22Blink%3ECSS%22> >> >> *Web Feature ID* >> CSSPseudoElement <https://webstatus.dev/features/CSSPseudoElement> >> >> *Motivation* >> Support for CSSPseudoElement - which is currently only defined for >> ::after, ::before, and ::marker - is now being extended to include several >> new pseudo-elements: ::backdrop: useful for closing a dialog when the >> backdrop is clicked, without interfering with clicks inside the dialog's >> content. This eliminates the need for complex intersection logic to >> determine where the click occurred. ::scroll-marker: can be used to collect >> click statistics. view transitions: enables geometry-aware view >> transitions.It also allows you to intercept a view transition mid-flight to >> start a new one, utilizing the coordinates of the currently animating >> element to avoid sudden visual jumps. >> >> *Initial public proposal* >> *No information provided* >> >> *TAG review* >> *No information provided* >> >> *TAG review status* >> Pending >> >> *Goals for experimentation* >> None >> >> *Risks* >> >> >> *Interoperability and Compatibility* >> *No information provided* >> >> *Gecko*: No signal ( >> https://github.com/mozilla/standards-positions/issues/1345) >> >> *WebKit*: No signal ( >> https://github.com/WebKit/standards-positions/issues/607) >> >> *Web developers*: No signals >> >> *Other signals*: >> >> *WebView application risks* >> >> Does this intent deprecate or change behavior of existing APIs, such that >> it has potentially high risk for Android WebView-based applications? >> *No information provided* >> >> >> *Debuggability* >> *No information provided* >> >> *Will this feature be supported on all six Blink platforms (Windows, Mac, >> Linux, ChromeOS, Android, and Android WebView)?* >> Yes >> >> *Is this feature fully tested by web-platform-tests >> <https://chromium.googlesource.com/chromium/src/+/main/docs/testing/web_platform_tests.md>?* >> Yes >> >> https://wpt.fyi/results/css/css-pseudo/backdrop-pseudo-element-click.tentative.html >> https://wpt.fyi/results/css/css-pseudo/CSSPseudoElement-view-transitions-scoped.tentative.html >> https://wpt.fyi/results/css/css-pseudo/CSSPseudoElement-view-transitions.tentative.html >> https://wpt.fyi/results/css/css-pseudo/events-on-pseudo-element-mutation.tentative.html >> >> *Flag name on about://flags* >> *No information provided* >> >> *Finch feature name* >> *No information provided* >> >> *Non-finch justification* >> *No information provided* >> >> *Rollout plan* >> Will ship enabled for all users >> >> *Requires code in //chrome?* >> False >> >> *Estimated milestones* >> DevTrial on desktop 147 >> DevTrial on Android 147 >> >> *Anticipated spec changes* >> >> Open questions about a feature may be a source of future web compat or >> interop issues. Please list open issues (e.g. links to known github issues >> in the project for the feature specification) whose resolution may >> introduce web compat/interop risk (e.g., changing to naming or structure of >> the API in a non-backward-compatible way). >> *No information provided* >> >> *Link to entry on the Chrome Platform Status* >> https://chromestatus.com/feature/6516055192240128?gate=6196512880197632 >> >> This intent message was generated by Chrome Platform Status >> <https://chromestatus.com>. >> > -- You received this message because you are subscribed to the Google Groups "blink-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAH3Z928TAaWtWB1O6SN6inj4nOFJcrqcS4ScGDyR8MdNPN08dQ%40mail.gmail.com.
