I'm curious what the reasoning was for sending this as a PSA vs I2S? Personally I'd be worried about websites specifying align-content on .foo but only expect it to be applied to flexboxes. Do we have a use counter for align-content on non-flexbox/grid?
Also, any plans for the other properties from https://drafts.csswg.org/css-align/ ? Christian On Mon, Dec 11, 2023 at 6:07 PM TAMURA, Kent <tk...@chromium.org> wrote: > Contact emailstk...@chromium.org, ikilpatr...@chromium.org > > Specificationhttps://drafts.csswg.org/css-align/#distribution-block > > Summary > > `align-content` CSS property works for block containers and table cells. > The property worked only for flex containers and grid containers. It > supports block containers and table cells, that is to say `display: block`, > `display: list-item`, `display: table-cell`, etc. > > > Blink componentBlink>Layout > <https://bugs.chromium.org/p/chromium/issues/list?q=component:Blink%3ELayout> > > Search tagscss <https://chromestatus.com/features#tags:css>, align-content > <https://chromestatus.com/features#tags:align-content> > > TAG reviewNone; API surface is not changed. > > TAG review statusNot applicable > > Risks > > > Interoperability and Compatibility > > Low risk. This just expands coverage of a CSS property. > > > *Gecko*: No signal > > *WebKit*: No signal > > *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? > > 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 > > https://wpt.fyi/results/css/css-align/blocks > https://wpt.fyi/results/css/css-align/multicol > > > Flag name on chrome://flagsAlignContentForBlocks > > Finch feature nameAlignContentForBlocks > > Requires code in //chrome?False > > Tracking bughttps://bugs.chromium.org/p/chromium/issues/detail?id=1500511 > > Estimated milestones > Shipping on desktop 122 > DevTrial on desktop 121 > Shipping on Android 122 > DevTrial on Android 121 > Shipping on WebView 122 > > 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/5159040328138752 > > This intent message was generated by Chrome Platform Status > <https://chromestatus.com/>. > > -- > TAMURA Kent > Software Engineer, Google > > > -- > 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/CAGH7WqFRawiS9g5UpYs4Nkh74MqQNdB4F2AMOdRJyC4Z-f2PUQ%40mail.gmail.com > <https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAGH7WqFRawiS9g5UpYs4Nkh74MqQNdB4F2AMOdRJyC4Z-f2PUQ%40mail.gmail.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/CAPTJ0XEV%2BDZO3Up2MxGn4FoA0j8%2Bh7%3D-j6kz13MM1h_jvYuJxg%40mail.gmail.com.
