@candera https://github.com/hoplon/hoplon/issues/238#issuecomment-362920150 ๐
@candera can you do a minimal repro with the latest hoplon?
maybe even try out https://github.com/hoplon/hoplon/issues/236#issuecomment-359178483
I will try to get to that. No promises. But, by the same token, no expectations that anyone spend any time fixing this.
i just wonder whether this is an issue in master
i was getting some weird edge cases when i actually wrote tests for merge-kids
(that are fixed now)
If you get really curious, I would imagine the repro isnโt too bad. You just need to have an element that has an attribute like :click and that doesnโt get added to the DOM immediately, or gets added and removed right away (not sure). You might not get 100% CPU like I am with just one element, but a profile should show you spending an awful lot of time in when-dom
โs doit
.
@candera i agree that ideally when-dom
is not time based
actually i'd like something that triggers on add and remove indefinitely
if you have a good idea i'm interested ๐
Check out that CSS hack above.
Because I tried the mutation observer thing and found it unimpressive.
you know i linked to the exact same article right? ๐
Now that you mention it, that does sound familiar. ๐
Sorry - as usual doing several things at the same time.
When in actuality Iโm lucky if I can do one halfway competently.
hah
well i didn't try it
i'd love to hear if it works