Closed Bug 1900412 Opened 2 years ago Closed 2 years ago

[wpt-sync] Sync PR 46596 - Allow writing-mode property in @page.

Categories

(Core :: Layout, task, P4)

task

Tracking

()

RESOLVED FIXED
128 Branch
Tracking Status
firefox128 --- fixed

People

(Reporter: wpt-sync, Unassigned)

References

()

Details

(Whiteboard: [wptsync downstream])

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

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

Morten Stenshorne <mstensho@chromium.org> wrote:

Allow writing-mode property in @page.

There are valid use cases for this inside @page margins, so it makes
sense to allow it for @page as well.

Bug: 40286153
Change-Id: If3433ec4b07d05e4335450e8e22ea43383da455a
Reviewed-on: https://chromium-review.googlesource.com/5587745
WPT-Export-Revision: 61845e6cf489413de8b52ce3ee14f12867699aa6

Component: web-platform-tests → Layout
Product: Testing → Core

CI Results

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

Total 1 tests

Status Summary

Firefox

FAIL: 1

Chrome

FAIL: 1

Links

Gecko CI (Treeherder)
GitHub PR Head
GitHub PR Base

Details

New Tests That Don't Pass

Pushed by wptsync@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/27ee1bd5861c [wpt PR 46596] - Allow writing-mode property in @page., a=testonly https://hg.mozilla.org/integration/autoland/rev/9f1fae91d686 [wpt PR 46596] - Update wpt metadata, a=testonly
Status: NEW → RESOLVED
Closed: 2 years ago
Resolution: --- → FIXED
Target Milestone: --- → 128 Branch
You need to log in before you can comment on or make changes to this bug.