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

Re: [matrix][cssom-view] DOMPoint, DOMPointLiteral definitions

From: Dirk Schulze <dschulze@adobe.com>
Date: Mon, 30 Sep 2013 11:12:14 -0700
To: "robert@ocallahan.org" <robert@ocallahan.org>
CC: Simon Pieters <simonp@opera.com>, www-style <www-style@w3.org>, Boris Zbarsky <bzbarsky@mit.edu>, "public-script-coord@w3.org" <public-script-coord@w3.org>
Message-ID: <3685FF47-4001-4D28-BBE8-05A7D6330973@adobe.com>

On Sep 30, 2013, at 7:56 PM, Robert O'Callahan <robert@ocallahan.org> wrote:

> On Tue, Oct 1, 2013 at 4:02 AM, Simon Pieters <simonp@opera.com> wrote:
> Do we need to differentiate between live/read-only and immutable at all?
> 
> In theory it could be useful for some clients to know when an object is immutable, because it means they can avoid copying it.
> 
> Currently we don't need DOMRectImmutable because AFAIK we don't have anything that would return an immutable rect. So we can avoid specifying it for now, and just specify DOMRect and DOMRectMutable.

We would have with SVG DOM. When we replace SVGRect with DOMRect, we should fix the behavior as well and let animVal return an immutable DOMRect.

Greetings,
Dirk

> 
> Rob
> -- 
> Jtehsauts  tshaei dS,o n" Wohfy  Mdaon  yhoaus  eanuttehrotraiitny  eovni le atrhtohu gthot sf oirng iyvoeu rs ihnesa.r"t sS?o  Whhei csha iids  teoa stiheer :p atroa lsyazye,d  'mYaonu,r  "sGients  uapr,e  tfaokreg iyvoeunr, 'm aotr  atnod  sgaoy ,h o'mGee.t"  uTph eann dt hwea lmka'n?  gBoutt  uIp  waanndt  wyeonut  thoo mken.o w  
Received on Monday, 30 September 2013 18:12:56 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:37:50 UTC