Seems unrelated to me. Should all HTML development stop until H2 kinks worked out?
-
-
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 @matthewcp and
HTML imports don't lean on H2 anymore than JS modules
1 reply 0 retweets 1 like -
Replying to @justinfagnani @bradleymeck and
The Polymer Bundler bundles HTML imports together.
1 reply 0 retweets 1 like -
Replying to @justinfagnani @bradleymeck and
See my comments about globalness.
1 reply 0 retweets 0 likes -
Replying to @wycats @justinfagnani and
Agree there, the fact that html modules are being worked on almost completely in secret is frustrating as an interested outsider.
3 replies 0 retweets 1 like -
Replying to @matthewcp @justinfagnani and
1: I think that's the nut of why they keep failing to get traction. It's not just the secrecy itself, it's also that it fails to acquire
1 reply 0 retweets 0 likes
2: important constraints from highly interested parties. Framework authors have been almost completely outside of the design process.
-
-
Replying to @wycats @matthewcp and
3: we're occasionally offered invites to try to persuade the real decision makers at Google but that's not sufficient to get the job done
1 reply 0 retweets 0 likes -
Replying to @wycats @matthewcp and
4/4: the design needs to be done collaboratively with the people who will have to interop, which includes but is not limited to frameworks.
0 replies 0 retweets 4 likes
End of conversation
New conversation -
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.