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

Re: Figuring out easier readonly interfaces

From: Anne van Kesteren <annevk@annevk.nl>
Date: Thu, 17 Oct 2013 10:15:20 +0100
Message-ID: <CADnb78hb2dXiPf6LAFioLL8anmsUErJZhZDAPE08=zw=m0du3w@mail.gmail.com>
To: "Mark S. Miller" <erights@google.com>
Cc: "Tab Atkins, Jr." <jackalmage@gmail.com>, "public-script-coord@w3.org" <public-script-coord@w3.org>, Allen Wirfs-Brock <allen@wirfs-brock.com>, "Robert O'Callahan" <robert@ocallahan.org>
On Mon, Oct 14, 2013 at 5:23 PM, Mark S. Miller <erights@google.com> wrote:
> The user agent is the browser, which can clearly modify any object it
> implements. Are we talking about user vs script, as in your <input readonly>
> example? Can the user modify a DOMRect object? If yes, and a user cannot
> modify a DOMRectReadOnly object, how can a DOMRect be a kind of
> DOMRectReadOnly?

Assuming the subclass has access to private state, that does not seem
surprising to me. The superclass only provides getters, the subclass
extends the superclass by providing setters.

I.e. the subclass augments the readonly API with a write API.

Received on Thursday, 17 October 2013 09:15:52 UTC

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