Sync web-platform-tests PR 23424 into mozilla-central (this bug is closed when the sync is complete).
Revert "[FlexNG] Make ComputeMinMaxSizes cache more precise."
This reverts commit 044aeb3ed3364905cc185d67eb947c7ca3c13741.
Reason for revert: Use-of-uninitialized-value.
Original change's description:
[FlexNG] Make ComputeMinMaxSizes cache more precise.
Previously our cache was imprecise, we recalculate our min/max sizes
when we didn't strictly need to, as we didn't know if we'd have a
%-block-size replaced element beneath us.
This patch changes ComputeMinMaxSizes to return a MinMaxSizesResult
(instead of just MinMaxSizes). This contains an additional bit of
information to indicate if this sub-tree depended on the %-block-size
given to it.
For most things, this will return false. For legacy layout roots we
always assume that they have children which depend on the %-block-size
(and why we initialize:
intrinsic_logical_widths_depends_on_percentage_block_size_ to true).
Along with this change, the cache changes in the following way:
- We store an addition bit of information on LayoutBox to store the bit
of information from ComputeMinMaxSizes.
- We calculate the %-block-size for our children up-front, this means
each of the algorithms don't have to do this.
- With these changes, the cache can now hit, when the %-block-size
given to us changes.
Commit-Queue: Ian Kilpatrick \<firstname.lastname@example.org>
Reviewed-by: Christian Biesinger \<email@example.com>
Reviewed-by: Morten Stenshorne \<firstname.lastname@example.org>
Reviewed-by: Koji Ishii \<email@example.com>
Reviewed-by: Balazs Engedy \<firstname.lastname@example.org>
Commit-Queue: Balazs Engedy \<email@example.com>