Bug 243173 - Update intrinsic sizing of flex containers (e.g. container max-content width) to new spec text
Summary: Update intrinsic sizing of flex containers (e.g. container max-content width)...
Status: NEW
Alias: None
Product: WebKit
Classification: Unclassified
Component: Layout and Rendering (show other bugs)
Version: WebKit Nightly Build
Hardware: Unspecified Unspecified
: P2 Normal
Assignee: Nobody
URL:
Keywords: BrowserCompat, InRadar
Depends on:
Blocks:
 
Reported: 2022-07-25 12:17 PDT by David Grogan
Modified: 2023-04-20 10:40 PDT (History)
6 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description David Grogan 2022-07-25 12:17:55 PDT 
All of the engines currently implement the same intrinsic size algorithm for flex containers, but it is not a good algorithm and it is not specified. Authors really want a better algorithm, and the spec calls for one in https://drafts.csswg.org/css-flexbox/#intrinsic-sizes.

Blink is planning to launch the new algorithm in the next few months, and it'd be great if the engines could sync up shipping to minimize breakage. We've talked about that some on the Firefox bug https://bugzilla.mozilla.org/show_bug.cgi?id=1055887.

I didn't see an existing WebKit bug for this, apologies if I missed it.

The chrome bugs for this are https://crbug.com/240765 and https://crbug.com/507397, which are the most starred flex bugs in our tracker.
Comment 1 David Grogan 2022-07-25 12:18:26 PDT 
Oh, the new algorithm would probably supersede this bug about the old algorithm https://bugs.webkit.org/show_bug.cgi?id=119113
Comment 2 Radar WebKit Bug Importer 2022-07-25 19:42:16 PDT 
<rdar://problem/97583061>