Scott Jehl on Nostr: Curious if there's any writing out there that I may have missed about attribute ...
Curious if there's any writing out there that I may have missed about attribute naming conventions/choices for custom elements? Current practices with attributes across WC frameworks and published components seems to be... just make up a reasonable name that isn't already a global HTML attribute. But what if that name collides with a future standard global attribute and ends up breaking things? Prefixes are common with element names but not attributes. Why? Any thoughts on this out there? Thx!
Published at
2024-06-26 14:30:56Event JSON
{
"id": "c8e33477b89dc7c2287de0a7a4135a32808e050e82f3c807506cdcd54c490083",
"pubkey": "8c72fb5d06a6a4442d62df9f481ff1f791e928589f247cf8932aaf42e0b6cdf2",
"created_at": 1719412256,
"kind": 1,
"tags": [
[
"proxy",
"https://mstdn.social/@scottjehl/112683401650288586",
"web"
],
[
"proxy",
"https://mstdn.social/users/scottjehl/statuses/112683401650288586",
"activitypub"
],
[
"L",
"pink.momostr"
],
[
"l",
"pink.momostr.activitypub:https://mstdn.social/users/scottjehl/statuses/112683401650288586",
"pink.momostr"
],
[
"expiration",
"1722004700"
]
],
"content": "Curious if there's any writing out there that I may have missed about attribute naming conventions/choices for custom elements? Current practices with attributes across WC frameworks and published components seems to be... just make up a reasonable name that isn't already a global HTML attribute. But what if that name collides with a future standard global attribute and ends up breaking things? Prefixes are common with element names but not attributes. Why? Any thoughts on this out there? Thx!",
"sig": "4c798938f7534c35c3b13c049aaf65eddfd61b455a3a41a464c2e9b851279611136ae8f745f34f52fa2c65228f5cb7f52a3b2aeaf560f6bc937deb886a4d0d18"
}
