- From: <bugzilla@jessica.w3.org>
- Date: Wed, 22 May 2013 22:51:53 +0000
- To: public-webapps-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=21886 --- Comment #10 from Dominic Cooney <dominicc@chromium.org> --- (In reply to comment #9) > The nominal reason the last argument is a dictionary is to allow this kind > of API expansion, correct? Yes. > We are being clever with the 'can be a dictionary-with-prototype OR a class' > trick, but it seems less than ideal to have that affect the design. > > In particular, if we come up with some other option, do we overload the API > further? Case-by-case, I assume. FWIW in the implementation in Blink a lot bifurcates on whether the custom element is a type extension or a custom tag. A similar situation might arise in scripts using document.register--you're either doing one or the other at any given point. > For these reasons, I'd be more inclined to let those options be static > members on the class. This is also fine from an implementor's point of view. -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Wednesday, 22 May 2013 22:51:58 UTC