Summary: | Flexbox container width being computed incorrectly | ||||||
---|---|---|---|---|---|---|---|
Product: | WebKit | Reporter: | Sammy Gill <sgill26> | ||||
Component: | Layout and Rendering | Assignee: | Nobody <webkit-unassigned> | ||||
Status: | RESOLVED FIXED | ||||||
Severity: | Normal | CC: | bfulgham, karlcow, simon.fraser, webkit-bug-importer, zalan | ||||
Priority: | P2 | Keywords: | BrowserCompat, InRadar | ||||
Version: | WebKit Nightly Build | ||||||
Hardware: | Unspecified | ||||||
OS: | Unspecified | ||||||
See Also: | https://github.com/web-platform-tests/wpt/pull/35714 | ||||||
Attachments: |
|
Pull request: https://github.com/WebKit/WebKit/pull/3423 Committed 254190@main (0599c10f9004): <https://commits.webkit.org/254190@main> Reviewed commits have been landed. Closing PR #3423 and removing active labels. *** Bug 243694 has been marked as a duplicate of this bug. *** |
Created attachment 461564 [details] Testcase It seems like we disagree on the Flexbox computed width in certain cases. In the example I am using, we compute a width of 180. I think this is from 100px (content) + 80 px (border and padding being added twice to the child which is another bug). Both Firefox and Chrome compute a container size of 65px (the border box size of the child). So it seems like there are 2 possible issues here: 1.) We are incorrectly computing an initial content size of 100px (Unless this is correct and both Firefox/Chrome are wrong) 2.) Incorrectly adding border+padding twice to child width