You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We should provide a small, lean DOM abstraction library which avoids dealing with some quirks like NodeList to Array conversion, event handler registration/deregistration and so on.
I definitely see this, but I'm not too sure, if we should really provide literal dom abstraction and if we should put it in an extra repository...
A few days ago, I had the idea to introduce a convention for that, which could be made part of the component API. Just a couple of reserved data-* attributes, like data-action="delete", which then would be available in component like:
We could reserve attributes data-action, data-input, data-result (without this being complete) and work with these... But I don't know if this would be too restricted.
So, a DOM abstraction might be the better solution. But it would also be a huge target for the old "reinventing the wheel" discussion. That's the reason why I'd like to go the extra step and remove some glue code, that the user would need to write anyway even with DOM abstraction and instead provide him/her with stable convention - All of which remains optional, because there still is direct access to the dom element.
We should provide a small, lean DOM abstraction library which avoids dealing with some quirks like NodeList to Array conversion, event handler registration/deregistration and so on.
Traversing
Event handling
Thoughts @grebaldi @Inkdpixels?
The text was updated successfully, but these errors were encountered: