03:05
<MikeSmith>
innovati: you know about https://whatwg.org/faq#adding-new-features, right?
03:06
<MikeSmith>
especially step #1
03:06
<MikeSmith>
> Forget about the particular solution you have in mind! Solution time is later!
03:07
<MikeSmith>
so the process is basically to not propose new global attributes at all, ever
03:07
<MikeSmith>
but instead, explain what problem you want solved
03:09
<MikeSmith>
and then in that context note that you think a new global attribute might be a solution the problem, and why
14:55
<innovati>
MikeSmith Expressing what I know doesn't really give me any new information. I can write something up, but I still wouldn't know if I'm completely wasting 100% of my time
14:57
<innovati>
I'm not trying to propose a feature today, I'm wondering about the feasibility of global attributes possibly happening if a good solution was found. If it's not feasible ever I would try to explore something that was more feasible instead
14:59
<innovati>
I was really hoping for some insight about global attributes and what it takes for one to be accepted, I believe each global attribute that can exist carries a small performance hit when creating new elements? If that's true you'd think they would aim to keep the list as short as possible for reasons. Those kinds of reasons and considerations around what global attributes cost and mean are what I'm hoping to learn
15:06
<innovati>
I'm helping to explore ways that things like ResizeObserver, MutationObserver, and IntersectionObserver might be utilized and controlled from CSS in a standard way, and part of that will need to be a way to target matching elements with selectors.
15:07
<innovati>
There are ways to wrote something like that which are valid CSS but incredibly unlikely to ever get standardized, and there are ways you could express it that are a much smaller ask and stand a better chance actually maybe becoming something
15:09
<innovati>
I'd like to try my best to stick as close to reality as possible :D