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

Re: Exposing constructors of readonly interfaces to web authors

From: Rik Cabanier <cabanier@gmail.com>
Date: Tue, 1 Jul 2014 08:08:26 +0200
Message-ID: <CAGN7qDCL2DWm9-Lj+DGtLxGy4rxGdqt-qnJUUdjFQG-MDi8EJQ@mail.gmail.com>
To: Ian Hickson <ian@hixie.ch>
Cc: "Robert O'Callahan" <robert@ocallahan.org>, Domenic Denicola <domenic@domenicdenicola.com>, "public-script-coord@w3.org" <public-script-coord@w3.org>
On Tue, Jul 1, 2014 at 6:08 AM, Ian Hickson <ian@hixie.ch> wrote:

> On Mon, 30 Jun 2014, Robert O'Callahan wrote:
> > >
> > > You're misunderstanding me. What I meant was, when taking as input an
> > > object to a spec algorithm, you should not say "it must be a DOMRect"
> > > (or ClientRect, or DOMRectReadOnly, or CommonSuperclassRect, or...).
> > > You should say "it has x, y, width, height properties." That has
> > > nothing to do with its class.
> >
> > I guess we would do that. Currently nothing takes a DOMRect(ReadOnly) as
> > an input, so this hasn't come up.
>
> The way we normally do _input_ (passing from JS to a DOM API) in Web IDL
> is to use a dictionary.
>

We tried that in one of the earlier proposals but this didn't allow us to
set up the inheritance scheme. We did leave DOMPointInit [1] in so you can
pass in objects with that signature
I believe dictionary members are also not allowed to be readonly in WebIDL.


1: http://dev.w3.org/fxtf/geometry/#dictdef-dompointinit
Received on Tuesday, 1 July 2014 06:08:55 UTC

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