In a new framework called e.g Foobar (2 letter abbreviation: fo) that uses many HTML attributes, what do you prefer for the attribute names?
-
-
Replying to @LeaVerou
would be nice to reserve attributes the way we reserved web components. <component-foo-bar> would have been silly.
1 reply 0 retweets 4 likes -
Replying to @wycats
There is a proposal on
@wicg_ that it gone largely ignored by the people in charge of HTML specs:https://discourse.wicg.io/t/relaxing-restrictions-on-custom-attribute-names/1444 …1 reply 5 retweets 3 likes -
how can we move it? And why are community groups the place proposals go to die?
2 replies 0 retweets 1 like -
An explainer on GitHub would be desirable, I think (problem + proposal + use cases); discussions per se are not compelling
2 replies 0 retweets 1 like -
Replying to @simevidas @LeaVerou
this feels pretty wrong for me. Understanding beyond the walls of google makes proposals better.
1 reply 0 retweets 0 likes
"we already have a solution" "WHY ARE YOU SO AGAINST IT" is like groundhog day at this point.
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.