Closed Bug 1857662 Opened 2 years ago Closed 2 years ago

[wpt-sync] Sync PR 42415 - [print] Don't use negative overflow for scaling.

Categories

(Core :: CSS Parsing and Computation, task, P4)

task

Tracking

()

RESOLVED FIXED
121 Branch
Tracking Status
firefox121 --- fixed

People

(Reporter: wpt-sync, Unassigned)

References

()

Details

(Whiteboard: [wptsync downstream])

Sync web-platform-tests PR 42415 into mozilla-central (this bug is closed when the sync is complete).

PR: https://github.com/web-platform-tests/wpt/pull/42415
Details from upstream follow.

Ian Kilpatrick <ikilpatrick@chromium.org> wrote:

[print] Don't use negative overflow for scaling.

Within ForceLayoutForPagination we used the LayoutOverflow on a
fragment to determine the total scale factor. This looked correct
however if we had negative overflow - we'd consider that in the
total width causing a large scale factor.

Instead of using Width()/Height(), use Right()/Bottom() (considering
only the "positive" overflow) for determining the total scale factor.

Bug: 1488825
Change-Id: Ib1dfb2e5f18d3032d99da2d06f99fb4f99a99a03

Reviewed-on: https://chromium-review.googlesource.com/4920061
WPT-Export-Revision: a35c855473d90503b465cac0127712c3ecd0b0a4

Component: web-platform-tests → CSS Parsing and Computation
Product: Testing → Core

CI Results

Ran 0 Firefox configurations based on mozilla-central, and Firefox, and Chrome on GitHub CI

Total 1 tests

Status Summary

Firefox

PASS: 1

Chrome

FAIL: 1

Links

GitHub PR Head
GitHub PR Base

Pushed by wptsync@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/a6fdf08a60da [wpt PR 42415] - [print] Don't use negative overflow for scaling., a=testonly
Status: NEW → RESOLVED
Closed: 2 years ago
Resolution: --- → FIXED
Target Milestone: --- → 121 Branch
You need to log in before you can comment on or make changes to this bug.