cc @mikeal this is what I was talking about the other day
-
-
Replying to @pfrazee @slightlylate
so, i dont think the optimal way to present functionality is to own the entire element creation pipeline.
1 reply 0 retweets 3 likes -
this immediately puts you in the framework world because in order to access you work is to call it in a specific way.
1 reply 0 retweets 4 likes -
once you give up on that and say “it’s just an element,” there are many ways to create an element.
2 replies 0 retweets 3 likes -
mmmm, but they are limited. You can't `const elem = new MyElement()` if you are extending HTMLElement.
2 replies 0 retweets 0 likes -
Of course you can. That was half the point of the exercise = )
1 reply 0 retweets 0 likes -
Replying to @slightlylate @bradleymeck and1 reply 0 retweets 1 like
-
Thats after it is in registry. I dont want to register mine.
2 replies 0 retweets 0 likes -
Is registration really the stumbling block? What's the tagName otherwise?
1 reply 0 retweets 0 likes -
why not undefined? my registry concerns stem from experience with global registration always ending up with collisions.
3 replies 0 retweets 0 likes
Because DOM (as a framework) enforces tagName/class mapping to enable (de)serialization.
-
-
if it wasn't global/string based I'd say thats fine, but serialization stays a blocker on using references, same for form IDREF attrs
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.
& Web Standards TL; Blink API OWNER
Named PWAs w/
DMs open. Tweets my own; press@google.com for official comms.