Re: Are web components *seriously* not namespaced?

2015-02-07 Thread Melvin Carvalho
On 5 February 2015 at 20:55, Tab Atkins Jr. wrote: > On Fri, Feb 6, 2015 at 12:48 AM, Glen wrote: > > So in other words it *is* a case of "it's good enough". Web components > are > > quite possibly the future of the web, and yet we're implementing them to > be > > "good enough" in "90%" of use c

[Bug 27975] New: [Custom]: No way to unregister a component

2015-02-07 Thread bugzilla
https://www.w3.org/Bugs/Public/show_bug.cgi?id=27975 Bug ID: 27975 Summary: [Custom]: No way to unregister a component Product: WebAppsWG Version: unspecified Hardware: PC OS: All Status: NEW Severity: nor

[Bug 27976] New: [Custom]: type extensions should be available as custom tags, not only through

2015-02-07 Thread bugzilla
https://www.w3.org/Bugs/Public/show_bug.cgi?id=27976 Bug ID: 27976 Summary: [Custom]: type extensions should be available as custom tags, not only through Product: WebAppsWG Version: unspecified Hardware: PC

[Bug 27977] New: [Custom]: mixin pattern: custom elements should be able to extend any base tag with is=

2015-02-07 Thread bugzilla
https://www.w3.org/Bugs/Public/show_bug.cgi?id=27977 Bug ID: 27977 Summary: [Custom]: mixin pattern: custom elements should be able to extend any base tag with is= Product: WebAppsWG Version: unspecified Hardware: PC

[Bug 27978] New: [Custom]: attachedCallback has no protocol for indicating that the custom tag is not applicable in this context

2015-02-07 Thread bugzilla
https://www.w3.org/Bugs/Public/show_bug.cgi?id=27978 Bug ID: 27978 Summary: [Custom]: attachedCallback has no protocol for indicating that the custom tag is not applicable in this context Product: WebAppsWG Versio