- From: <bugzilla@jessica.w3.org>
- Date: Tue, 22 Jan 2013 23:35:37 +0000
- To: public-webapps-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=20487 --- Comment #7 from Dimitri Glazkov <dglazkov@chromium.org> --- (In reply to comment #6) > > I think it does. > > No, I don't think it would. You're right. > > Furthermore the current text does not allow that sort of thing anyway, since > it requires that prototypes "inherit from HTMLElement.prototype", whatever > that means. It sure sounds like deriving things from SVG elements is > excluded, though. Aside from incorrect wording, I am wondering if I should ignore SVG elements, at least for now. Ian pointed out that ideally, it should be possible to create custom SVG elements as well, but there's a lot of complexity that starts creeping here once I open that pandora's box. I have no intention to ever introduce namespaces here, so it should be possible to add SVG support later: the custom element namespace would be resolved based on inherited interface. WDYT? -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Tuesday, 22 January 2013 23:35:39 UTC