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 04:08:21 +0000 (UTC)
To: Robert O'Callahan <robert@ocallahan.org>
cc: Domenic Denicola <domenic@domenicdenicola.com>, "public-script-coord@w3.org" <public-script-coord@w3.org>
Message-ID: <alpine.DEB.2.00.1407010406540.1057@ps20323.dreamhostps.com>
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.

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

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