To expand: use-cases that are not satisfied by the available user-land implementations. (Or ones that are but would benefit from this being in Node.js core.)
-
-
Replying to @apapirovski
Web Components prerender is my primary desire. Somewhat possible in userland but bigger idea here is Node as a first class user agent makes it have proper “skin in the game” that is the web platform.
2 replies 0 retweets 9 likes -
Replying to @brianleroux
on
#webcomponents ... do you know a way/polyfill/alternative to make customized built-ins useful, cross-browser?1 reply 0 retweets 0 likes -
Replying to @wolframkriesing
Idk but from what I understand
@WebReflection’s custom elements impl the best if you’re shipping to production1 reply 0 retweets 1 like -
Replying to @brianleroux @WebReflection
thanks! that looks like it supports CBE, I will try ... https://github.com/WebReflection/document-register-element#whats-new-in-custom-elements-v1 … i was looking at https://github.com/webcomponents/custom-elements/pull/88 … all the time and that seems up in the air
1 reply 0 retweets 1 like -
Replying to @wolframkriesing @brianleroux
heads up: custom elements builtin are a ghost in the specification ... fully unsupported and nowhere in the process of being concretely standardized. Current API regarding CE and builtin extends is dead already.
1 reply 0 retweets 1 like -
Replying to @WebReflection @brianleroux
Ok, Thanks for sharing that. I saw the discussion going nowhere. Too bad though.
1 reply 0 retweets 0 likes -
What is the current best practice for extending a native element? Feels like the the right thing for what I currently need to solve.
1 reply 0 retweets 0 likes -
I think
@polymer has a very good summary of the situation and a way how to move forward with it. https://www.polymer-project.org/2.0/docs/about_20#type-extension …#webcomponents#cbe1 reply 1 retweet 1 like -
Yeaaah I’m not sure what happened. I liked `is` but
Cc @slightlylate1 reply 0 retweets 1 like
@briankardell has been writing up what happened on the way to the Forum; TL;DR: if the point is to reduce magic and improve reuse, we can only really get there through further decomposition.
-
-
Replying to @slightlylate @brianleroux and
I.e., behaviours from built-in that you want to re-use should be factored out into mixins that the built-in elements also happen to use.
3 replies 0 retweets 1 like -
Replying to @slightlylate @wolframkriesing and
Makes sense. Inherited behaviour would turn into an accessibility nightmare whereas it just gets retained by composition (I am assuming).
1 reply 0 retweets 1 like - 1 more reply
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.
& Web Standards TL; Blink API OWNER
Named PWAs w/
DMs open. Tweets my own; press@google.com for official comms.