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

Re: Figuring out easier readonly interfaces

From: Simon Pieters <simonp@opera.com>
Date: Thu, 17 Oct 2013 11:10:08 +0200
To: "Mark S. Miller" <erights@google.com>
Cc: "robert@ocallahan.org" <robert@ocallahan.org>, "Dirk Schulze" <dschulze@adobe.com>, "Anne van Kesteren" <annevk@annevk.nl>, "Tab Atkins Jr." <jackalmage@gmail.com>, "Allen Wirfs-Brock" <allen@wirfs-brock.com>, "public-script-coord@w3.org" <public-script-coord@w3.org>
Message-ID: <op.w43c26qqidj3kv@simons-macbook-pro.local>
On Thu, 17 Oct 2013 01:21:36 +0200, Mark S. Miller <erights@google.com>  

>> Readonly doesn't mean immutable or constant.
> No one said it did. That would be silly ;).
> Read only means that, through this object, changes to some underlying  
> state
> can be observed but not caused. In order for changes to be observed, it
> must be possible to cause those changes, but holding this object is not  
> by
> itself adequate to cause those changes.

OK, then I misunderstood the argument. Sorry.

Is the problem here that a mutable DOMRect instance has DOMRectReadOnly in  
the prototype chain, which is a lie?

Simon Pieters
Opera Software
Received on Thursday, 17 October 2013 09:10:44 UTC

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