I haven't heard about imports much lately and Gecko's implementation was removed (dvcs, so, "removed"). @littlecalculist and @annevk, wdyt?
-
-
There is interest in the HTML modules idea. We also wanted to see how JS modules and service workers potentially change the design.
2 replies 1 retweet 2 likes -
Mozilla is not the lone holdout though. Other than Google nobody has been convinced thus far. Only Mozilla communicated as much.
1 reply 0 retweets 0 likes -
I continue to be pretty skeptical of HTML imports, especially considering all of the bundling work in the framework space.
3 replies 0 retweets 3 likes -
Skeptical is good. It just feels prematurely written off entirely.
1 reply 0 retweets 3 likes -
There's already plenty in flight. Let's wrap up the things with good consensus before opening up another front.
1 reply 0 retweets 2 likes -
1 reply 0 retweets 0 likes
-
Seems unrelated to me. Should all HTML development stop until H2 kinks worked out?
1 reply 0 retweets 1 like -
Replying to @matthewcp @dalmaer and
1. Not unrelated, since HTML Imports leans enough on H2 that the kinks matter. 2. There are "kinks" in other parts of the WC suite
2 replies 0 retweets 0 likes -
Replying to @wycats @matthewcp and
The number of "kinks" and relatively low level of adoption of the entire suite justifies firming things up before adding more complexity
2 replies 0 retweets 1 like
Not to mention the fact that HTML Imports are probably the least well motivated part of the WC suite.
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.