W3C home > Mailing lists > Public > public-script-coord@w3.org > January to March 2011

RE: Removal of identifierless getters, setters, etc.

From: Travis Leithead <Travis.Leithead@microsoft.com>
Date: Thu, 17 Mar 2011 16:40:47 +0000
To: Cameron McCormack <cam@mcc.id.au>, "public-script-coord@w3.org" <public-script-coord@w3.org>
Message-ID: <9768D477C67135458BF978A45BCF9B381741986B@TK5EX14MBXW602.wingroup.windeploy.ntdev.microsoft.com>
I was apparently at the meeting, but can't remember the rationale either...



-----Original Message-----
From: public-script-coord-request@w3.org [mailto:public-script-coord-request@w3.org] On Behalf Of Cameron McCormack
Sent: Tuesday, October 12, 2010 2:24 PM
To: public-script-coord@w3.org
Subject: Removal of identifierless getters, setters, etc.

At TPAC last year, there was a discussion on Web IDL that resulted in a resolution to remove special operations (getters, setters, etc.) that have no identifier:

  http://www.w3.org/2009/11/02-webapps-minutes.html#item06


I don’t see any rationale there, so I wonder if anyone who was there could explain?

HTML5 currently uses a number of these, specifically:

  DOMStringMap - name getter, setter, creator & deleter
  HTMLDocument - name getter
  Window - name getter, index getter
  TimedTrackCueList - index getter
  CanvasPixelArray - index getter, index setter

Would the idea here be to given all of these an identifier but to declare them as omittable (so that in JS real method wouldn’t exist on these objects anyway)?

Thanks,

Cameron

--
Cameron McCormack ≝ http://mcc.id.au/



Received on Thursday, 17 March 2011 16:41:21 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 8 May 2013 19:30:03 UTC