- From: Domenic Denicola <notifications@github.com>
- Date: Thu, 03 Mar 2016 10:21:11 -0800
- To: w3c/webcomponents <webcomponents@noreply.github.com>
Received on Thursday, 3 March 2016 18:22:04 UTC
Yeah, I was saying in https://github.com/w3c/webcomponents/issues/369#issuecomment-191754665 that I was not ok with (4). It should either be unambiguous or required. It sounds like we should go with (1). The remaining questions to me are: - What should `otherDoc.defineElement` do? Always throw, or operate on a shared registry with its "creator document"? - What should `otherDoc.createElement("custom-element")` and the parser in that other doc do? HTMLUnknownElement, or use a shared registry? The current spec shares the registry. If we want to continue with that, maybe we should move the registry to window instead of document... `document.defineElement` is looking like a stranger and stranger API, as opposed to `window.defineElement`. --- Reply to this email directly or view it on GitHub: https://github.com/w3c/webcomponents/issues/369#issuecomment-191894115
Received on Thursday, 3 March 2016 18:22:04 UTC