Mozilla is not the lone holdout though. Other than Google nobody has been convinced thus far. Only Mozilla communicated as much.
-
-
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 -
Do HTML Imports lean on H2 more than JS modules?
2 replies 0 retweets 1 like -
Replying to @matthewcp @wycats and
IDK if you can inline HTML Imports as is like ESM (rollup / webpack / etc.)
2 replies 0 retweets 0 likes -
Replying to @bradleymeck @wycats and
HTML imports are irrelevant, being rewritten, so possibilities are what we define them to be.
2 replies 0 retweets 0 likes
The globalness of HTML Imports is a real problem. If we're revisiting... <div><import tags="x-foo" from="specifier" /><x-foo /></div>
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.