LGTM1 On Wed, Sep 4, 2024 at 2:42 AM Chromestatus <ad...@cr-status.appspotmail.com> wrote:
> Contact emails msten...@chromium.org > > Explainer None > > Specification https://www.w3.org/TR/css-break-3/#break-decoration > > Summary > > Support box-decoration-break:clone both for inline fragmentation (line > layout) and block fragmentation (pagination for printing, multicol). > Traditionally in Blink, only box-decoration-break:slice (the initial value) > has been supported for block fragmentation, whereas for inline > fragmentation, box-decoration-break:clone was also supported, but only when > using the prefixed -webkit-box-decoration-break property. See > https://drafts.csswg.org/css-break/#break-decoration > > > Blink component Blink>Layout > <https://bugs.chromium.org/p/chromium/issues/list?q=component:Blink%3ELayout> > > TAG review None > > TAG review status Not applicable > > Risks > > > Interoperability and Compatibility > > Low. > > > *Gecko*: Shipped/Shipping > > *WebKit*: No signal ( > https://github.com/WebKit/standards-positions/issues/366) Currently > WebKit and Blink only support -webkit-box-decoration-break, and only for > inline fragmentation (i.e. no block fragmentation). > > *Web developers*: No signals (https://issues.chromium.org/issues/40415661) > > > *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? > > None > > > Debuggability > > None > > > 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 > > Flag name on chrome://flags > > Finch feature name BoxDecorationBreak > > Requires code in //chrome? False > > Tracking bug https://issues.chromium.org/issues/41295617 > > Estimated milestones > Shipping on desktop 130 > DevTrial on desktop 129 > Shipping on Android 130 > DevTrial on Android 129 > Shipping on WebView 130 > > 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). > None > > Link to entry on the Chrome Platform Status > https://chromestatus.com/feature/5162398704205824?gate=6467793951391744 > > Links to previous Intent discussions Intent to Prototype: > https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAKWZFm4fXc%3D%2BF68yXQ41-V8seHYj%2BjKT4VLNhCgyz7V_feZGBQ%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/00000000000012c165062147fe77%40google.com > <https://groups.google.com/a/chromium.org/d/msgid/blink-dev/00000000000012c165062147fe77%40google.com?utm_medium=email&utm_source=footer> > . > -- 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/CAOMQ%2Bw8fFNrTKO%3DZnf_mtbEpW979Qzk22KPhVP_HTammnbdt1g%40mail.gmail.com.
