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: Mon, 14 Oct 2013 14:58:05 +0100
Message-ID: <CADnb78g9y5mtsQ4C=h=rFdHDUNZj_8jt1kvrK1X0HmP=z_aO9A@mail.gmail.com>
To: "Mark S. Miller" <erights@google.com>
Cc: "Robert O'Callahan" <robert@ocallahan.org>, "Tab Atkins Jr." <jackalmage@gmail.com>, Allen Wirfs-Brock <allen@wirfs-brock.com>, "public-script-coord@w3.org" <public-script-coord@w3.org>
On Mon, Oct 14, 2013 at 2:40 PM, Mark S. Miller <erights@google.com> wrote:
> On Mon, Oct 14, 2013 at 2:16 AM, Robert O'Callahan <robert@ocallahan.org>
> wrote:
>> "DOMRectReadOnly" means that this interface provides only read access to
>> the object. It says nothing about whether there are ways to mutate the
>> object, whether through other interfaces on the same object or via related
>> DOM objects (e.g. when a DOMRectReadOnly is returned by the "bounds"
>> attribute of a mutable DOMQuad). This name may be confusing,
> The notion that the "Only" in the name refers only to the interface and not
> the object is confusing and bizarre. None of "DOM", "Rect", or "Read" refer
> to the interface, they all refer to the object.

We have the same notion elsewhere though. E.g. a <input readonly>
cannot be modified by the user, but can be modified through script.
Attributes annotated in IDL with "readonly" have the same behavior.

Received on Monday, 14 October 2013 13:58:33 UTC

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