Web-Facing Change PSA: align-content CSS property for blocks

[TAMURA, Kent]

Contact emails

tk...@chromium.org, ikilp...@chromium.org

Specification

https://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 component

Blink>Layout

Search tags

css, align-content

TAG review

None; API surface is not changed.

TAG review status

Not 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?

Yes

https://wpt.fyi/results/css/css-align/blocks https://wpt.fyi/results/css/css-align/multicol

Flag name on chrome://flags

AlignContentForBlocks

Finch feature name

AlignContentForBlocks

Requires code in //chrome?

False

Tracking bug

https://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.

--

TAMURA Kent
Software Engineer, Google

[PhistucK]

> Low risk. This just expands coverage of a CSS property.

Well... Not that low, perhaps?

I think I used a trick (I suppose) where under some circumstances, I do not want the property (and others that are flexbox-specific) to have any effect, so I just change display to block. Not saying it is a great way to do things, but it does mean that there might be others like me.

The risk is usually only due to potential visual glitches for the most part, I suppose, but it might be more than that (things being hidden/unreachable).

☆PhistucK

--
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+...@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.

[一丝]

WebKit is being actively implemented: https://github.com/WebKit/WebKit/pull/21522

以上

一丝

PhistucK <phis...@gmail.com> 于2023年12月12日周二 07:50写道：

To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CABc02_%2BKngSYY2afeLa5RHU4XEcmn_mmj3hx_T0AWADg8BHH_Q%40mail.gmail.com.

[Vladimir Levin]

It's worthwhile to file a request for position here as well to ensure there are no concerns -- unless the position is already expressed elsewhere

 

To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CA%2B-d5Zq%2BX3S8ETrv%3Dxbzyuo%3D5yKvTsNRsYxqBWMxhWDQP-4EaA%40mail.gmail.com.

[Christian Biesinger]

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

[TAMURA, Kent]

You're right.  This change can break sites in such cases.  Though we don't have a use counter, we think the number of affected sites should be small, and the breakage is a minor rendering difference. So two API owners, chrishtr@ and tkent@, thought a PSA was enough for this.

We might expand supported conditions of other properties of css-align.

[TAMURA, Kent]

Thank you for the suggestion.  I filed https://github.com/mozilla/standards-positions/issues/941 .