TAG review: https://github.com/w3ctag/design-reviews/issues/824 WebKit standards position: https://github.com/WebKit/standards-positions/issues/147 Mozilla standards position: https://github.com/mozilla/standards-positions/issues/762
On Wed, Mar 15, 2023 at 1:37 PM Joey Arhar <jar...@chromium.org> wrote: > Contact emailsfla...@chromium.org, jar...@chromium.org > > Explainer > https://github.com/w3c/csswg-drafts/issues/6429#issuecomment-1318933547 > > Specificationhttps://drafts.csswg.org/css-display-4/#display-animation > > Summary > > Support specifying display and content-visibility in animations. This > support allows for developers to create exit animations after which the > element automatically becomes display: none or content-visibility: hidden > without needing to write any javascript to handle that switch after the > animation is finished. This allows exit animations for elements to be added > purely in CSS. > > > Blink componentBlink>Animation > <https://bugs.chromium.org/p/chromium/issues/list?q=component:Blink%3EAnimation> > > TAG reviewNone > > TAG review statusNot applicable > > Risks > > > Interoperability and Compatibility > > Developers may have display specified in existing animations which would > start being included in their animation after this change. > > > *Gecko*: No signal > > *WebKit*: No signal > > *Web developers*: Positive ( > https://front-end.social/@mia/109433817951030826) > > *Other signals*: > > Ergonomics > > This will be used in tandem with popover/dialog elements and the > CSSTransitionDiscrete feature. Usage of this feature will not make it hard > for chrome to maintain good performance. > > > Activation > > It will not be challenging for developers to use this feature immediately. > > > Security > > This doesn't extend developer capabilities beyond styles the developer > could set via existing CSS or scripts. > > > 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? > > This is not high risk for WebView, but is controlled by a base::Feature > anyway. > > > Debuggability > > This feature extends the capabilities of existing css animations, css > transitions and web animations and will show amongst other developer > animations. > > > Will this feature be supported on all six Blink platforms (Windows, Mac, > Linux, Chrome OS, 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 > > Flag nameCSSDisplayAnimation > > Requires code in //chrome?False > > Tracking bughttps://bugs.chromium.org/p/chromium/issues/detail?id=1395394 > > MeasurementThis feature does not have any UseCounters. > > Availability expectationI'm not sure when this will be implemented in > safari and firefox. I don't think that they have started implementing this > yet, but we only very recently got this resolved in CSSWG. > > Adoption expectationThis will be the best practice for animating the > entry and exit if dialogs and popovers immediately. > > Adoption planI don't have an adoption plan. > > Non-OSS dependencies > > Does the feature depend on any code or APIs outside the Chromium open > source repository and its open-source dependencies to function? > This feature does not depend on anything outside of chromium. > > Sample linkshttps://output.jsbin.com/buquher > > Estimated milestones > M114 > > 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). > This change has been specced and I don't think any more changes to the > spec will happen. > > Link to entry on the Chrome Platform Status > https://chromestatus.com/feature/5154958272364544 > > Links to previous Intent discussionsIntent to prototype: > https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAJh39TMCg_NwX3apO7K2t%3DauPVKXWwF9B2RHbkE6yfjCNc8a1w%40mail.gmail.com > > > 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 blink-dev+unsubscr...@chromium.org. To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAK6btw%2BfQHkpoG-cSUF%3DJOTvua7CjX8euRjUjD6DGrm-TJo%3DdQ%40mail.gmail.com.
