Closed Bug 1510061 Opened 2 years ago Closed 2 years ago

[wpt-sync] Sync PR 14240 - CSS: WPTs for Positioned Layout parsing

Categories

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

enhancement

Tracking

()

RESOLVED FIXED
mozilla66
Tracking Status
firefox66 --- fixed

People

(Reporter: mozilla.org, Unassigned)

References

()

Details

(Whiteboard: [wptsync downstream])

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

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

Eric Willigers <ericwilligers@chromium.org> wrote:
>  CSS: WPTs for Positioned Layout parsing
>  
>  Test parsing and computed value for
>  https://drafts.csswg.org/css-position/
>  
>  - bottom left right top
>  - position
>  - z-index
>  - inset-after inset-before inset-end inset-start (not currently implemented)
>  
>  Change-Id: I586271fe584fadb19e5683a2781c32142fd9001a
>  Reviewed-on: https://chromium-review.googlesource.com/1350409
>  WPT-Export-Revision: 4d8585272b4b7ab68abb93c266954a321cc14885
Component: web-platform-tests → CSS Parsing and Computation
Product: Testing → Core
Ran 30 tests and 120 subtests
OK     : 30
PASS   : 99
FAIL   : 21

New tests that have failures or other problems:
/css/css-position/parsing/bottom-computed.html
    Property bottom value 'calc(50% + 60px)' computes to 'calc(50% + 60px)': FAIL
/css/css-position/parsing/inset-after-valid.html
    e.style['inset-after'] = "-10px" should set the property value: FAIL
    e.style['inset-after'] = "-20%" should set the property value: FAIL
    e.style['inset-after'] = "auto" should set the property value: FAIL
    e.style['inset-after'] = "calc(2em + 3ex)" should set the property value: FAIL
/css/css-position/parsing/inset-before-valid.html
    e.style['inset-before'] = "-10px" should set the property value: FAIL
    e.style['inset-before'] = "-20%" should set the property value: FAIL
    e.style['inset-before'] = "auto" should set the property value: FAIL
    e.style['inset-before'] = "calc(2em + 3ex)" should set the property value: FAIL
/css/css-position/parsing/inset-end-valid.html
    e.style['inset-end'] = "-10px" should set the property value: FAIL
    e.style['inset-end'] = "-20%" should set the property value: FAIL
    e.style['inset-end'] = "auto" should set the property value: FAIL
    e.style['inset-end'] = "calc(2em + 3ex)" should set the property value: FAIL
/css/css-position/parsing/inset-start-valid.html
    e.style['inset-start'] = "-10px" should set the property value: FAIL
    e.style['inset-start'] = "-20%" should set the property value: FAIL
    e.style['inset-start'] = "auto" should set the property value: FAIL
    e.style['inset-start'] = "calc(2em + 3ex)" should set the property value: FAIL
/css/css-position/parsing/left-computed.html
    Property left value 'calc(50% + 60px)' computes to 'calc(50% + 60px)': FAIL
/css/css-position/parsing/right-computed.html
    Property right value 'calc(50% + 60px)' computes to 'calc(50% + 60px)': FAIL
/css/css-position/parsing/top-computed.html
    Property top value 'calc(50% + 60px)' computes to 'calc(50% + 60px)': FAIL
/css/css-position/parsing/z-index-invalid.html
    e.style['z-index'] = "calc(0.5)" should not set the property value: FAIL
Pushed by wptsync@mozilla.com:
https://hg.mozilla.org/integration/mozilla-inbound/rev/58b8d41e9b59
[wpt PR 14240] - CSS: WPTs for Positioned Layout parsing, a=testonly
https://hg.mozilla.org/integration/mozilla-inbound/rev/f6b9756d68b0
[wpt PR 14240] - Update wpt metadata, a=testonly
Pushed by james@hoppipolla.co.uk:
https://hg.mozilla.org/integration/mozilla-inbound/rev/fa55ea9ce705
[wpt PR 14240] - CSS: WPTs for Positioned Layout parsing, a=testonly
https://hg.mozilla.org/integration/mozilla-inbound/rev/bbdf0c639e08
[wpt PR 14240] - Update wpt metadata, a=testonly
https://hg.mozilla.org/mozilla-central/rev/fa55ea9ce705
https://hg.mozilla.org/mozilla-central/rev/bbdf0c639e08
Status: NEW → RESOLVED
Closed: 2 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla66
You need to log in before you can comment on or make changes to this bug.