Closed Bug 1456309 Opened 5 years ago Closed 5 years ago

[wpt-sync] Sync PR 10592 - Update DOMPoint and DOMQuad tests


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




Tracking Status
firefox61 --- fixed


(Reporter:, Unassigned)




(Whiteboard: [wptsync downstream])

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

Details from upstream follow.

Chris Nardi <> wrote:
>  Update DOMPoint and DOMQuad tests
>  Per, DOMPoint's constructor accepts zero to four values, and DOMPointReadOnly has the exact same constructor. Additionally, DOMQuad no longer has a live bounds attribute per, instead replacing it with `getBounds()` which cannot be set. Fix tests of DOMPoint and DOMQuad to reflect these changes.
Component: web-platform-tests → CSS Parsing and Computation
Product: Testing → Core
Ran 3 tests and 97 subtests
OK     : 3
PASS   : 57
FAIL   : 40

Existing tests that now have a worse result (e.g. they used to PASS and now FAIL):
    testConstructor1: FAIL
    boundsAttribute0: bounds: FAIL
    p1Top4Attributes0: bounds: FAIL
    p1Top4Attributes1: bounds: FAIL
    testConstructor0: bounds: FAIL
    testConstructor10: bounds: FAIL
    testConstructor11: bounds: FAIL
    testConstructor12: bounds: FAIL
    testConstructor13: bounds: FAIL
    testConstructor14: bounds: FAIL
    testConstructor16: bounds: FAIL
    testConstructor5: bounds: FAIL
    testConstructor6: bounds: FAIL
    testConstructor7: bounds: FAIL
    testConstructor8: bounds: FAIL
    testConstructor9: bounds: FAIL

New tests that have failures or other problems:
    DOMPointReadOnly constructor with 4 values: FAIL
    DOMPointReadOnly constructor with no values: FAIL
    DOMQuad bounds must be nuked: FAIL
Pushed by
[wpt PR 10592] - Update DOMPoint and DOMQuad tests, a=testonly
[wpt PR 10592] - Update wpt metadata, a=testonly
Closed: 5 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla61
You need to log in before you can comment on or make changes to this bug.