mastodontech.de ist einer von vielen unabhängigen Mastodon-Servern, mit dem du dich im Fediverse beteiligen kannst.
Offen für alle (über 16) und bereitgestellt von Markus'Blog

Serverstatistik:

1,5 Tsd.
aktive Profile

#webcomponents

2 Beiträge2 Beteiligte0 Beiträge heute
Antwortete im Thread

@leaverou These all power HTML in some way or other...

- Scoped Custom Element Registries
- Reference Target API
- elementInternals.type github.com/MicrosoftEdge/MSEdg
- Declarative CSS Modules and the adoptedstylesheets attribute github.com/MicrosoftEdge/MSEdg
- Declarative Partial Updates github.com/WICG/declarative-pa
- DOM Parts
- Platform based windowing/virtualization
- <tabs>

I've got lots more for CSS/JS if you get signed up for those.

Good luck with the survey!

Home for explainer documents originated by the Microsoft Edge team - MicrosoftEdge/MSEdgeExplainers
GitHubMSEdgeExplainers/ElementInternalsType/explainer.md at main · MicrosoftEdge/MSEdgeExplainersHome for explainer documents originated by the Microsoft Edge team - MicrosoftEdge/MSEdgeExplainers

In custom elements, is it best to create one MutationObserver that handles every instance of the custom element or observers per instance, then set up and tear down the observer inside the custom element lifecycle? The target would be the custom element itself (or something within its shadow tree). #WebComponents #WebPerf

thanks to a discussion on reddit [1] and some links [2] I came across a different view on .
In short, just wrap content in a instead of trying to "upgrade" it. Like so:

<user-avatar>
<img src>
</user-avatar>

I always thought until now that it should rather be

<img src is=user-avatar>

but `is` is not widely usable.
I still need to digest it. I see the use cases, but somehow feels still strange

[1] reddit.com/r/HTML/comments/1ld
[2] adactio.com/journal/20618