Contact emailsdgro...@chromium.org

ExplainerBehaves as 100%, except it sizes the margin box regardless of the
value of box-sizing.
<https://drafts.csswg.org/css-sizing-4/#stretch-fit-sizing:~:text=Behaves%20as%20100%25%2C%20except%20it%20sizes%20the%20margin%20box%20regardless%20of%20the%20value%20of%20box%2Dsizing.>

Specificationhttps://drafts.csswg.org/css-sizing-4/#sizing-values

Summary

A keyword for CSS sizing properties (e.g. 'width', 'height') that allows
elements to grow to exactly fill their containing block's available space.
It is similar to '100%', except the resulting size is applied to the
element's margin box instead of the box indicated by 'box-sizing'. Using
this keyword allows the element to keep its margins while still being as
large as possible. An unprefixed version of '-webkit-fill-available'.


Blink componentBlink>Layout
<https://issues.chromium.org/issues?q=customfield1222907:%22Blink%3ELayout%22>

Search tagsstretch <https://chromestatus.com/features#tags:stretch>, fill
<https://chromestatus.com/features#tags:fill>

TAG reviewNone

TAG review statusNot applicable

Risks


Interoperability and Compatibility

Each of the three major engines already has a rough implementation of this
feature from before it was specified. (Named -moz-available and
-webkit-fill-available). The three behaviors are not interoperable. The
intention of this new 'stretch' keyword is to align the engines on this
specified behavior which differs slightly from each of the prefixed
versions. We expect the behavior of this feature to be fully interoperable.
Gecko has taken part in the specification discussions (e.g.
https://github.com/w3c/csswg-drafts/issues/11044) and has contributed tests
(https://bugzilla.mozilla.org/show_bug.cgi?id=1937624)


*Gecko*: Positive (
https://github.com/mozilla/standards-positions/issues/1054)

*WebKit*: No signal (
https://github.com/WebKit/standards-positions/issues/401)

*Web developers*: Positive (
https://github.com/web-platform-tests/interop/issues/726) An author
requested this to be part of Interop2025. Lots of +1 on the chrome bug.

*Other signals*:

Ergonomics

None


Activation

Nope. Will be usable immediately


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

Existing CSS and layout devtools panel works fine.


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-sizing/stretch?label=master&label=experimental&product=chrome&product=firefox&product=safari&aligned&view=subtest&q=sizing%2Fstretch


Flag name on about://flagsNone

Finch feature nameLayoutStretch

Requires code in //chrome?False

Tracking bughttps://crbug.com/41253915

Availability expectationGecko has started work and will probably finish in
< 1 year.

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

Estimated milestones
Shipping on desktop 136
Shipping on Android 136
Shipping on WebView 136

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).
https://github.com/w3c/csswg-drafts/issues/4028 -- There is consensus among
members of Apple, Mozilla, and Google on the issue. No significant
arguments against the proposal that we followed (
https://github.com/w3c/csswg-drafts/issues/4028#issuecomment-2372348130)

Link to entry on the Chrome Platform Status
https://chromestatus.com/feature/6176445286842368?gate=5489036266045440

Links to previous Intent discussionsIntent to Prototype:
https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAOZbSt31nVWJNsfA0v30YGbceWr-M1sSYMoUFKBKMGw%2B7XzR%2BQ%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 visit 
https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAOZbSt3yu1nWUZM7jK1cNoS60hwLfhvO0vE1w5fM6f2FS%3Do9Vg%40mail.gmail.com.

Reply via email to