W3C home > Mailing lists > Public > public-script-coord@w3.org > October to December 2012

[Bug 20225] don't allow overridden operations and attribute getters/setters to be invoked on descendant objects

From: <bugzilla@jessica.w3.org>
Date: Fri, 07 Dec 2012 03:25:15 +0000
To: public-script-coord@w3.org
Message-ID: <bug-20225-3890-aSxVwwNPrT@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=20225

Boris Zbarsky <bzbarsky@mit.edu> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |annevk@annevk.nl

--- Comment #12 from Boris Zbarsky <bzbarsky@mit.edu> ---
The method as defined at
http://dom.spec.whatwg.org/#dom-htmlcollection-nameditem makes sense for an
HTMLPropertiesCollection as far as it goes, no?

But note that HTMLCollection defines the return value to be "object" precisely
so that people who want to define other behavior can.  If we're not planning to
make use of that functionality, we should change HTMLCollection to just return
Element? from namedItem and let places that want to return something else
override the method as you're doing here.

Basically, either we should be using the extensibility hook that DOMCore
already provides here or we should stop providing that hook if it has no
consumers.  The current situation leads to confusion because people have to
start worrying about why the hook is being provided and whether they're reading
the spec right.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
Received on Friday, 7 December 2012 03:25:18 UTC

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