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.
-
-
Makes sense. Inherited behaviour would turn into an accessibility nightmare whereas it just gets retained by composition (I am assuming).
-
This Tweet is unavailable.
New conversation -
-
-
That means `is=` is history, and agreed to not become reality? /me trying to figure out which future proof way to go ;)
-
personally feel
@WebReflection has the best plan for this https://medium.com/@WebReflection/a-custom-elements-v0-grampafill-dc1319420e9b … (tho I'm sure some won't agree / but it is really smart from a migration perspective)
End of conversation
New conversation -
-
-
sounds like the thing that https://elix.org/ is doing ... cc
@JanMiksovsky -
We'd love to see what
@slightlylate suggests: platform-provided mixins that can be combined to add built-in behavior to custom elements. Instead of defining new HTML elements with complex behavior (e.g., dialog), mixins to provide such behavior would be more useful and flexible.
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.
& Web Standards TL; Blink API OWNER
Named PWAs w/
DMs open. Tweets my own; press@google.com for official comms.
Cc