This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
As we settled most of the detail for the HTML Imports v1 in the spec [1], I think it's time to start merging the spec into HTML. The remaining sub-bugs of Bug 20683 are almost about how it should fit into the HTML spec. I'd like to ask how we should move this forward. [1] http://w3c.github.io/webcomponents/spec/imports/
Note that we've already discussed about this before. - https://www.w3.org/Bugs/Public/show_bug.cgi?id=24643 - https://www.w3.org/Bugs/Public/show_bug.cgi?id=24667
Roger. What's the implementation status? (So I know which browsers to reverse-engineer when I spec it, and how much to rely on the spec vs the implementations.)
(In reply to Ian 'Hixie' Hickson from comment #2) > Roger. Thank you, Sir!! > What's the implementation status? (So I know which browsers to > reverse-engineer when I spec it, and how much to rely on the spec vs the > implementations.) Chrome implements current spec as is (at least tries to be as is). Mozilla is working on it but there is nothing we can play with yet.
Any idea who I should speak to on the Mozilla side? BTW, do you know if the text in that spec was exclusively written by Google employees?
(In reply to Ian 'Hixie' Hickson from comment #4) > Any idea who I should speak to on the Mozilla side? I think Gabor Krizsanits is that person but you can ask here for sure: https://bugzilla.mozilla.org/show_bug.cgi?id=877072 > > BTW, do you know if the text in that spec was exclusively written by Google > employees? Dimitri and I, both are Google employees, are the only authors of the spec.
The Gecko implementation slowly converges to the spec. as well, the script execution order is the biggest challenge currently. I hope I can get to it next week... So the reverse engineering of the current patch might be a bit too early, but I'm happy to talk to you about it any time!
Spoke with dglazkov about this. I need to wait until bug 25715 is resolved before I can integrate this, to avoid us ending up with two separate dependency resolution systems.
This is blocked on getting improvements to ES to define regular script loading. Once I've redefined how regular script loading works, I can define how to integrate with module loading and so on, and then I'll be able to add this.
I've not been making much progress convincing es-discuss of the need for changes, which is putting this in jeopardy. http://esdiscuss.org/topic/es6-loader-proposed-changes
+dherman Dave, anything we can do to move this along? Should we organize an modules/imports summit and try to hash this out?
Sounds good. Need to have at least Yehuda Katz participate, and possibly one or two others. We can set up video chat for anyone remote. Dave
(In reply to Dave Herman from comment #11) > Sounds good. Need to have at least Yehuda Katz participate, and possibly one > or two others. We can set up video chat for anyone remote. > > Dave Awesome. How does the first week of October look for you peeps?
Looks good to me; Dave?
I propose October 6 or 7 at Google in Mountain View + VC (Hangouts) for anyone remote. We can start at around 12:30pm, right after lunch, approx. duration 2 hours. WDYT? Please RSVP and I'll get the room situated.
I'm not sure if we can do it that week. I need to send an email to Yehuda's colleagues to help us schedule his time. Dave
(In reply to Dave Herman from comment #15) > I'm not sure if we can do it that week. I need to send an email to Yehuda's > colleagues to help us schedule his time. > > Dave Ok. Can you propose some times that would work you folks? I will adapt.
I thought we had agreement to just drop the HTML Imports feature for now (at least as currently specced). If that is in fact the case, then I suggest that this bug be closed. And if there are already plans for a new take on (declarative?) imports, then I think a new issue should be opened at https://github.com/whatwg/html/issues if/when there’s a new concrete spec/proposal to consider. If others feel that we shouldn’t just close this, please chime in here.
(In reply to Michael[tm] Smith from comment #17) > I thought we had agreement to just drop the HTML Imports feature for now (at > least as currently specced). If that is in fact the case, then I suggest > that this bug be closed. And if there are already plans for a new take on > (declarative?) imports, then I think a new issue should be opened at > https://github.com/whatwg/html/issues if/when there’s a new concrete > spec/proposal to consider. > > If others feel that we shouldn’t just close this, please chime in here. I certainly wasn't part of this agreement. However, I think it's okay to close this bug.
Yeah, I think comment 17 overstates things. But perhaps it is better to say that HTML Imports as specced does not have consensus and so it is premature to talk about merging it into HTML. So yeah, let's close this and open a new issue on GitHub when/if a consensus-having spec is produced.