W3C home > Mailing lists > Public > public-script-coord@w3.org > July to September 2014

Re: [geometry] DOMRectList with legacy

From: Rik Cabanier <cabanier@gmail.com>
Date: Thu, 17 Jul 2014 09:56:13 -0700
Message-ID: <CAGN7qDAwZPG+ONUp+DOkMEgLkxFACQxkKR-227wLVcvxqk-bhQ@mail.gmail.com>
To: Boris Zbarsky <bzbarsky@mit.edu>
Cc: Anne van Kesteren <annevk@annevk.nl>, Dirk Schulze <dschulze@adobe.com>, "public-script-coord@w3.org" <public-script-coord@w3.org>, FX <public-fx@w3.org>
On Thu, Jul 17, 2014 at 5:56 AM, Boris Zbarsky <bzbarsky@mit.edu> wrote:

> On 7/17/14, 4:08 AM, Anne van Kesteren wrote:
>
>> Adding [ArrayClass] to a few legacy classes
>> does not help much.
>>
>
> Well, it gives you map(), foreach(), every(), some(), filter(), reduce().
>
> That's not nothing....  It seems to me that in cases when it's
> web-compatible, having [ArrayClass] on legacy lists is strictly better than
> not having it.


Making the legacy DOMRectList an [ArrayClass] wouldn't be web-compatible.
IE, WebKit and Blink don't implement it as an array class unlike Firefox.
Since this is a legacy interface, why not just specify what everyone has
implemented and leave it at that?
Received on Thursday, 17 July 2014 16:56:41 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:14:22 UTC