Hi!
I have a strange bug that I believe may be caused from Blaze.
I have an HTML table where each tr corresponds to Reactive Documents from a Subscription. The trs are in an {{each}} Template helper.
Each tr has HTML inputs for columns. Where each column represents a property in the document. There’s a feature where editing an Input and leaving the field (so using jQuery blur event), will update the full document .
The blur event is captured by a template event. I’m noticing however, that I can leave field1 and click into field2. This should just trigger blur on field1. However - sometimes a consecutive blur is triggered on field2.
I commented out the actual Update code on the Server and verified that this prevents the bug. So this led me to believe that the weirdness is happening somewhere in the Reactivity.
Any insights? Or - how could I debug further into Blaze itself? I want to basically see how this false positive of blur on field2 was called - i.e. it’d be great to get stacktrace of where the blur event got triggered and then work backwards. Thanks!