Closed Bug 1477215 Opened 4 years ago Closed 4 years ago

[wpt-sync] Sync PR 12088 - CSS: scroll properties do not accept unitless lengths

Categories

(Core :: Layout, enhancement, P4)

enhancement

Tracking

()

RESOLVED FIXED
mozilla63
Tracking Status
firefox63 --- fixed

People

(Reporter: mozilla.org, Unassigned)

References

()

Details

(Whiteboard: [wptsync downstream])

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

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

Eric Willigers <ericwilligers@chromium.org> wrote:
>  CSS: scroll properties do not accept unitless lengths
>  
>  The following properties no longer accept unitless lengths in quirks mode:
>  scroll-margin-block-end
>  scroll-margin-block-start
>  scroll-margin-bottom
>  scroll-margin-inline-end
>  scroll-margin-inline-start
>  scroll-margin-left
>  scroll-margin-right
>  scroll-margin-top
>  scroll-padding-block-end
>  scroll-padding-block-start
>  scroll-padding-bottom
>  scroll-padding-inline-end
>  scroll-padding-inline-start
>  scroll-padding-left
>  scroll-padding-right
>  scroll-padding-top
>  
>  The only properties that should accept unitless lengths in quirks mode
>  are listed in
>  https://quirks.spec.whatwg.org/#the-unitless-length-quirk
>  
>  
>  BUG=865889
>  
>  Change-Id: Id700932eda312dc0292b2c4a25ddbb57f2f99aa9
>  Reviewed-on: https://chromium-review.googlesource.com/1144991
>  WPT-Export-Revision: 09817becb63747f7c814ed7c4af4f1d12a4566b1
Component: web-platform-tests → Layout
Product: Testing → Core
Ran 1 tests and 30 subtests
OK     : 1
PASS   : 30
Pushed by james@hoppipolla.co.uk:
https://hg.mozilla.org/integration/mozilla-inbound/rev/e58377cd9c62
[wpt PR 12088] - CSS: scroll properties do not accept unitless lengths, a=testonly
https://hg.mozilla.org/mozilla-central/rev/e58377cd9c62
Status: NEW → RESOLVED
Closed: 4 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla63
You need to log in before you can comment on or make changes to this bug.