Re: [w3c/webcomponents] HTML modules spec draft editorial feedback (#783)

I've pushed an update to the [proposed spec changes doc](https://github.com/w3c/webcomponents/blob/gh-pages/proposals/html-module-spec-changes.md) that addresses most of this feedback as well as other improvements and corrections.  The description for [the PR](https://github.com/w3c/webcomponents/pull/793) outlines the highlights.

The biggest thing not yet addressed is the move of HTML Module Record's definition to the HTML5 spec.  It's not yet clear to me what this cross-spec inheritence should look like, or exactly what the final API surface for each spec should be.  However I've tried to push all the HTML-specific stuff over to that spec (knowledge of documents, inline/external scripts, etc).  A key bit of this is that the construction of HTML Module Records is all on the HTML side since that requires knowledge of documents and script elements.  ES just uses the finished structure that's passed over, whose only indication that it knows anything about HTML DOM is in the name `ScriptEntry`, which should probably be changed; I haven't thought of something better yet.

Thanks for reviewing the documents!

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/webcomponents/issues/783#issuecomment-464231950