Scott Jehl on Nostr: I suspect that MDN's custom elements guide has led many web components newcomers to ...
I suspect that MDN's custom elements guide has led many web components newcomers to early disappointment. It leads with customized built-ins as the first of two enhancement paths, and showcases some great examples that use them via [is=""]. It takes some digging (or testing) to learn Webkit doesn't implement that part of the standard. By then, you might've thought built-ins would be the primary way you'd bind enhancements! But then, the guide does follow the standard
https://developer.mozilla.org/en-US/docs/Web/API/Web_components/Using_custom_elementsPublished at
2024-06-03 16:07:55Event JSON
{
"id": "9323b3203e01183a9ee59b9f173ac2821db145394f392c81488b31f12c22c13d",
"pubkey": "b366513fe344d7bcd092cb92e8dbb8f07ef6321dbdf1a05fd3439b0ba381c150",
"created_at": 1717430875,
"kind": 1,
"tags": [
[
"proxy",
"https://mstdn.social/users/scottjehl/statuses/112553549888352461",
"activitypub"
]
],
"content": "I suspect that MDN's custom elements guide has led many web components newcomers to early disappointment. It leads with customized built-ins as the first of two enhancement paths, and showcases some great examples that use them via [is=\"\"]. It takes some digging (or testing) to learn Webkit doesn't implement that part of the standard. By then, you might've thought built-ins would be the primary way you'd bind enhancements! But then, the guide does follow the standard\nhttps://developer.mozilla.org/en-US/docs/Web/API/Web_components/Using_custom_elements",
"sig": "0d863de84ad2626566fb4548aaa5b5a3605a8eb38b6dbcd05abe3fcc810b719fc47c04cfcc81c2819757aefc41281c1492bffffbd376bb5cb7fa4abb5f458bd1"
}
