RE: How to specify an object that can be mutable or immutable from Domenic Denicola on 2013-09-26 (public-script-coord@w3.org from July to September 2013)

From: Domenic Denicola <domenic@domenicdenicola.com>
Date: Thu, 26 Sep 2013 14:06:50 +0000
To: Simon Pieters <simonp@opera.com>, Dirk Schulze <dschulze@adobe.com>
CC: "robert@ocallahan.org" <robert@ocallahan.org>, "public-script-coord@w3.org" <public-script-coord@w3.org>
Message-ID: <B4AE8F4E86E26C47AC407D49872F6F9F9B256771@BY2PRD0510MB354.namprd05.prod.outlook.>

From: Simon Pieters [simonp@opera.com]

> We support that for DOMPoint (by also defining a dictionary), but not for DOMRect. I think if we want to do this everywhere, it's better to change WebIDL to allow user objects than to define dictionaries for everything. Does it make sense everywhere? It doesn't make sense for e.g. Node#appendChild().

Some conversions fail on all inputs except those posessing a certain brand; some conversions work more generically. The conversion to Node would be one of the former; the conversion to a normalized rect type would be one of the latter. As another example of the latter, the conversion to string (defined by `input+""`) succeeds on all inputs except those with throwing `toString` methods.

Received on Thursday, 26 September 2013 14:07:23 UTC