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

RE: Exposing constructors of readonly interfaces to web authors

From: Ian Hickson <ian@hixie.ch>
Date: Tue, 1 Jul 2014 20:33:20 +0000 (UTC)
To: Domenic Denicola <domenic@domenicdenicola.com>
cc: Rik Cabanier <cabanier@gmail.com>, Dirk Schulze <dschulze@adobe.com>, Robert O'Callahan <robert@ocallahan.org>, "public-script-coord@w3.org" <public-script-coord@w3.org>
Message-ID: <alpine.DEB.2.00.1407012032030.9426@ps20323.dreamhostps.com>
On Tue, 1 Jul 2014, Domenic Denicola wrote:
> I see several problems with the readonly class, at least in the DOMRect case:
> - It is not constructable
> - Its values can change through magic, but users cannot change them

Why are these bad?

(It's not magic, it's just that the object is implemented by the browser.)

The whole Web API works this way. Being consistent with how the Web works 
seems relatively important for authoring sanity. It's what authors are 
familiar with.

Ian Hickson               U+1047E                )\._.,--....,'``.    fL
http://ln.hixie.ch/       U+263A                /,   _.. \   _\  ;`._ ,.
Things that are impossible just take longer.   `._.-(,_..'--(,_..'`-.;.'
Received on Tuesday, 1 July 2014 20:33:58 UTC

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