Closed Bug 1767599 Opened 3 years ago Closed 3 years ago

[wpt-sync] Sync PR 33928 - Set body margin to 0

Categories

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

Product:
Core
Component:
CSS Parsing and Computation
Type:
task

Tracking

()

Status:
RESOLVED FIXED
Milestone:
102 Branch
Tracking Flags:
Tracking Status
firefox102 --- fixed

People

(Reporter: wpt-sync, Unassigned)

References

(
URL
)

Details

(Whiteboard: [wptsync downstream])

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

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

Mike <mike@qtunes.org> wrote:

Set body margin to 0

The 8px default margin on the body means the float with "3" in it overruns the first page, onto page 2. As the next float (with "4" in it) has a break-before: page, it should be rendered on page 3.

Currently it's not in Chrome or Firefox, but that's an implementation issue and doesn't mean the test is correct.

This sets the body margin to 0, to ensure the reftest only renders onto two pages.

Component: web-platform-tests → CSS Parsing and Computation
Product: Testing → Core
Whiteboard: [wptsync downstream] → [wptsync downstream error]
Whiteboard: [wptsync downstream error] → [wptsync downstream]
Whiteboard: [wptsync downstream] → [wptsync downstream error]
Whiteboard: [wptsync downstream error] → [wptsync downstream]
Whiteboard: [wptsync downstream] → [wptsync downstream error]
Whiteboard: [wptsync downstream error] → [wptsync downstream]
Whiteboard: [wptsync downstream] → [wptsync downstream error]
Whiteboard: [wptsync downstream error] → [wptsync downstream]
Whiteboard: [wptsync downstream] → [wptsync downstream error]
Whiteboard: [wptsync downstream error] → [wptsync downstream]
Pushed by wptsync@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/3c88a1d4d204 [wpt PR 33928] - Set body margin to 0, a=testonly
Test result changes from PR not available.

https://hg.mozilla.org/mozilla-central/rev/3c88a1d4d204

Status: NEW → RESOLVED
Closed: 3 years ago
status-firefox102: --- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 102 Branch
You need to log in before you can comment on or make changes to this bug.