- From: <bugzilla@jessica.w3.org>
- Date: Mon, 07 Jan 2013 23:42:45 +0000
- To: public-webapps-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=20225 --- Comment #17 from Cameron McCormack <cam@mcc.id.au> --- It is probably easier to solve this without a Web IDL solution, and just avoid defining interfaces that cause operations/attributes from ancestor interfaces to not work on them. (I changed my mind about not allowing overridden operations to be invoked on descendant objects -- I think (again) it is just poor interface design.) (In reply to comment #16) > I'd be happy to change namedItem() on HTMLCollection back to 'Element?'. The two reasonable solutions that don't involve changing Web IDL are (1) to make HTMLCollection work use 'object?', and define the interface to be a more general collection, and particular instances define what items go in the collection, and (2) to change namedItem() to 'Element?' and have HTMLPropertiesCollection not inherit from HTMLCollection. I'd be happy with either. -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Monday, 7 January 2013 23:42:47 UTC