[wpt-sync] Sync PR 46862 - Don't clamp fragmentation block-size if it actually fits.
Categories
(Core :: Layout, task, P4)
Tracking
()
Tracking | Status | |
---|---|---|
firefox129 | --- | fixed |
People
(Reporter: wpt-sync, Unassigned)
References
()
Details
(Whiteboard: [wptsync downstream])
Sync web-platform-tests PR 46862 into mozilla-central (this bug is closed when the sync is complete).
PR: https://github.com/web-platform-tests/wpt/pull/46862
Details from upstream follow.
Morten Stenshorne <mstensho@chromium.org> wrote:
Don't clamp fragmentation block-size if it actually fits.
The code that called SetIsBlockSizeForFragmentationClamped() incorrectly
assumed that we had (so far) decided not to move past the fragment, but
this wasn't checked. This would cause the block-size for fragmentation
to be clamped, setting an incorrect BlockSizeForFragmentation()
(LayoutResult), which in turn could result in false cache hits: a
fragment would appear to fit within the new and smaller fragmentatainer
block-size, although it didn't.Bug: 348445899
Change-Id: Ia7b74ba4861c341d1236bafcf881d6745ce0c161
Reviewed-on: https://chromium-review.googlesource.com/5645005
WPT-Export-Revision: 28b1fd1020a3b9a448a4aecfe7bdc58c7461db27
Assignee | ||
Updated•3 months ago
|
Assignee | ||
Comment 1•3 months ago
|
||
Assignee | ||
Comment 2•3 months ago
|
||
CI Results
Ran 9 Firefox configurations based on mozilla-central, and Firefox, Chrome, and Safari on GitHub CI
Total 1 tests
Status Summary
Firefox
PASS
: 1
Chrome
FAIL
: 1
Safari
PASS
: 1
Links
Comment 4•3 months ago
|
||
bugherder |
Description
•