Closed Bug 1454622 Opened Last year Closed 3 months ago
Change DOMQuad bounds to get
Bounds() as per specification
Spec: https://drafts.fxtf.org/geometry/#dom-domquad-getbounds Gecko implements .bounds instead of .getBounds(). Chromium and WebKit implement .getBounds(). Test that needs fixing to change .bounds to .getBounds(): http://w3c-test.org/css/geometry/DOMQuad-001.html Test that uses getBounds(): http://w3c-test.org/css/geometry/DOMQuad-002.html Should also add .bounds to http://w3c-test.org/css/geometry/historical.html
This isn't just a naming matter. The two getters have totally different semantics ([SameObject] vs [NewObject]). Would need to carefully audit all code using this getter to see whether it's OK with that change. In practice, we should probably ship getBounds(), convert internal consumers, then work on telemetry for .bounds or something...
In bug 1186265, I'm marking .bounds as deprecated and adding telemetry to give us an idea of how used it is. Hopefully we'll be able to remove it in a few releases.
https://telemetry.mozilla.org/new-pipeline/dist.html#!cumulative=0&end_date=2018-08-02&keys=__none__!__none__!__none__&max_channel_version=nightly%252F63&measure=USE_COUNTER2_DEPRECATED_DOMQuadBoundsAttr_PAGE&min_channel_version=nightly%252F60&processType=*&product=Firefox&sanitize=1&sort_keys=submissions&start_date=2018-06-25&table=0&trim=1&use_submission_date=0 looks pretty unused.
Created web-platform-tests PR https://github.com/web-platform-tests/wpt/pull/17693 for changes under testing/web-platform/tests
Upstream PR merged
You need to log in before you can comment on or make changes to this bug.