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

[Bug 12845] Disallow shadowing attributes

From: <bugzilla@jessica.w3.org>
Date: Thu, 09 Jun 2011 00:07:45 +0000
To: public-script-coord@w3.org
Message-Id: <E1QUSmn-0004H4-9K@jessica.w3.org>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=12845

--- Comment #25 from Cameron McCormack <cam@mcc.id.au> 2011-06-09 00:07:41 UTC ---
One example of the kind of thing I was thinking about was how objects
stringify.  Now, this isn't directly applicable because this is done with
"stringifiers" in Web IDL as opposed to writing a toString operation, and
besides operations are different from attributes -- but I think it's an
analagous situation.

To me, Allen's general pattern of derived things doing additional work (like
logging) makes sense to allow.  So I think we want to "allow these sort of spec
bugs" only if there could never be non-buggy reasons for shadowing.

All of this applies equally to operations too, right?

The examples from HTML5 are deliberate, as far as I know, and not accidental
shadowing.  Maybe Ian can say why it's preferable to have these properties on
HTMLElement rather than on the separate interfaces where they actually apply.

-- 
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
Received on Thursday, 9 June 2011 00:07:46 UTC

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