With data attributes, any current browser supports the dataset property on the dom object... so e.target.dataset.id instead of e.target.getAttribute('data-id')
Other than that, the useCallback method is interresting at least.
I tend to prefer data attributes (dataset) because then it renders and is able to be utilized by ui/integration test frameworks.
Cool, hadn't dug into this, but seems interresting. Don't know that I'd use it outside of an appImage, unsure if there are packaging options, or FS limitations that are similar in Mac/Windows.
Are any of the dynamic/js based swf modules reasonable for this? I know it's not quite the same.
Deno uses https typically... I like the change myself... hoping this leads to better compatability with deno... or at least with deno, maybe importing `npm+node:...` since it's node-style modules from npm. And have deno auto-include the node compatibility shims.
That said, deno has become much more of a goto for me the past few months alone... there's only a handful of things I haven't found implemented that I need... it's been a nicer experience for orchestration scripting.
With data attributes, any current browser supports the dataset property on the dom object... so e.target.dataset.id instead of e.target.getAttribute('data-id') Other than that, the useCallback method is interresting at least. I tend to prefer data attributes (dataset) because then it renders and is able to be utilized by ui/integration test frameworks.