Issue metadata
Sign in to add a comment
|
Remove DOMRectList
Reported by
metaj...@gmail.com,
Apr 24 2017
|
||||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_4) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/57.0.2987.133 Safari/537.36 Steps to reproduce the problem: 1. Create a new Range object 2. Call getClientRects() on the object 3. Note that resulting list implements item() method from DOMRectList What is the expected behavior? The spec was changed to sequence<ClientRect>, so the result should be a normal array. What went wrong? The spec was changed but the implementations haven't been updated yet. Did this work before? N/A Does this work in other browsers? No Firefox still implements this but there is a bug filed to remove it: https://bugzilla.mozilla.org/show_bug.cgi?id=1335726 Chrome version: 57.0.2987.133 Channel: stable OS Version: OS X 10.12.4 Flash Version: Spec changes discussed here: https://www.w3.org/Bugs/Public/show_bug.cgi?id=26200
,
May 23 2017
This is a case where the spec changed a couple of years ago, but no browser has implemented the change. It does look like the Web Platform Tests for CSSOM is the place it might be used in Chrome (https://cs.chromium.org/search/?q=domrectlist+package:%5Echromium$&type=cs), but that it's not actually in use in our code. It looks like getClientRects actually returns a ClientRectList, and it should be updated to a Sequence in Source/core/dom/Range.idl and Source/core/dom/Element.idl?
,
Jul 11 2017
|
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by tkent@chromium.org
, May 18 2017