develwoutacause’s Twitter Archive

9 results for WebComponents

1. develwoutacause’s Twitter Archive—№ 1,577

   Some thoughts on a potential #SSR-based future of #WebComponents. https://github.com/w3c/webcomponents-cg/discussions/39#discussioncomment-3418724. github.com/w3c/webcomponents-cg/discussions/39#discussioncomment-3418724

2. develwoutacause’s Twitter Archive—№ 1,373

   Some thoughts about #SSR-ing #webcomponents from my experience with rules_prerender and some of the challenges a general solution will need to overcome. https://github.com/webcomponents-cg/community-protocols/issues/7#issuecomment-1134001778. github.com/webcomponents-cg/community-protocols/issues/7#issuecomment-1134001778

3. develwoutacause’s Twitter Archive—№ 1,541

   tag as a possible #JavaScript-less approach to #SSR'd #WebComponents. I just realized I can easily prototype that proposal, so I did! https://blog.dwac.dev/posts/html-fragments/#ecosystem. blog.dwac.dev/posts/html-fragments/#ecosystem

4. develwoutacause’s Twitter Archive—№ 336

   the last couple hours trying to configure #Storybook. However, it's #WebComponents documentation lacks any examples and is minimal at best. @OpenWc stuff doesn't work out of the box, lacks types,

5. develwoutacause’s Twitter Archive—№ 1,685

   Can #WebComponents Twitter help me out with this one? I found some baffling upgrade behavior. It seems that creating a custom element in a different document *deletes* existing non-defined properties