Kristian Dalgård

> Additionally – as have been argued by plenty of people – there's simply **no place** for Google Analytics inside a browser extension. Concretely, the standard should be something like...

I think a better fix would be triggering the `change` event manually inside the binding. What do you think?

Thanks for the debugging effort. I'll look into it first thing, probably later today.

@wvanooijen92 Do you use GroundDB as well?

If you set a custom attribute on one of those elements in dev tools, does the attribute disappear after the reconnect, meaning that the element is re-rendered?

I swapped jQuery for vanilla `removeEventListener` in `1.0.0` – would it be possible for you to downgrade to `0.9.4` and check if the problem is there, too? I suspect that...

Hum...

Let me know about the custom attributes. I definitely think you've found the correct part of the code to look at, but I'm having trouble reproducing the bug simply with...

Good point, but in that case @wvanooijen92 has the same combination.

No reason for apology. It's definitely caused by some detail that has to do with the computation – what you call re-evaluation.