W3C home > Mailing lists > Public > public-fx@w3.org > July to September 2015

Re: ClientRectList.item() usage is very low in Blink

From: Philip Jägenstedt <philipj@opera.com>
Date: Wed, 1 Jul 2015 23:51:39 +0200
Message-ID: <CAMQvoC=EJMKVLupYhT-DacQjvGGo-A9205LBfnRH-Dv=0iTh_A@mail.gmail.com>
To: "Tab Atkins Jr." <jackalmage@gmail.com>
Cc: "public-fx@w3.org" <public-fx@w3.org>, www-style list <www-style@w3.org>
On Thu, May 28, 2015 at 12:02 AM, Tab Atkins Jr. <jackalmage@gmail.com> wrote:
> On Wed, May 27, 2015 at 6:21 AM, Philip Jägenstedt <philipj@opera.com> wrote:
>> http://dev.w3.org/fxtf/geometry/ says "The DOMRectList interface is
>> at-risk. The authors of this specification await feedback from
>> implementers if the item() function of DOMRectList is currently in use
>> on legacy interfaces. If there is no/not enough content to justify
>> DOMRectList, legacy interfaces must use sequences instead and
>> DOMRectList will be removed from this specification."
>> Chrome 43 reached the stable channel about a week ago, and it had a
>> use counter in Blink to answer this very question:
>> https://www.chromestatus.com/metrics/feature/timeline/popularity/694
>> Compare that to another use counter also in the same release:
>> https://www.chromestatus.com/metrics/feature/timeline/popularity/696
>> When usage rounds to zero as for ClientRectList.item(), it means that
>> <0.0001% of page loads are affected. This is no guarantee that
>> replacing ClientRectList with sequence<ClientRect> as the return value
>> of Element.getClientRects() and Range.getClientRects() would be safe,
>> but it's promising.
>> (Dirk Schulze suggested that I notify public-fx and www-style.)
> Excellent news. Thanks, Philip!

Is this issue being tracked somehow, do I need to do something or can
I sit back and wait?

Received on Wednesday, 1 July 2015 21:52:07 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:49:54 UTC