I personally used AMD modules together with HTML Imports.
-
-
Replying to @justinfagnani
Most of the chatter ive been interested in revolves around the no-js side of things. Though scoping is still prob there
1 reply 0 retweets 0 likes -
Replying to @bradleymeck
Yes, and this is admittedly an area that existing HTML Imports didn't address well...
1 reply 0 retweets 0 likes -
Replying to @justinfagnani @bradleymeck
...but since there's no "include" functionality there wasn't that much need for a reference between files. Custom elements work via tagname.
1 reply 0 retweets 0 likes -
Replying to @justinfagnani
Which I think will eventually lead us back to XML Namespaces which lead to DTD ...
2 replies 0 retweets 0 likes -
Replying to @bradleymeck @justinfagnani
Or maybe something like <import names="tag tag tag" from="url"> Not a joke. Something like this is worth exploring.
2 replies 0 retweets 2 likes -
Replying to @wycats @bradleymeck
Considering that HTML Modules would use the same loader and modules semantics as JS, it makes sense for the import syntax to be similar too.
1 reply 0 retweets 1 like -
Question is: what's the scope being imported _into_?
1 reply 0 retweets 0 likes -
Replying to @justinfagnani @wycats
Parent tag? That might not work w/ people using <head> though.
2 replies 0 retweets 0 likes -
Replying to @bradleymeck @justinfagnani
I like something like this: <import tag="foo" from="src"> <loading>...</loading> <loaded>...</loaded> <error>...</error> <import>
1 reply 0 retweets 0 likes
With default behavior with only one block meaning loaded.
-
-
Could also have an <imports> tag to allow many imports in one place with a single <loaded>
0 replies 0 retweets 0 likesThanks. Twitter will use this to make your timeline better. UndoUndo
-
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.