@evaldas, you can call
enableFormTracking again - it is safe to do so multiple times
This will only work for form elements which exist when it is called. If you are creating a form programatically, call
enableFormTrackingagain after adding it to the document to track it. (You can call
enableFormTrackingmultiple times without risk of duplicated events.)
@ihor yes this works for new dynamic forms, but doesn’t work for new fields added to existing forms like when some field is only available after user fills in some text. This is to prevent adding duplicate event listener for submit_form; Ideally you would want to form events and form element events to be handled independently.
I think your suggestion is sensible, it’s not my call whether or not it would be roadmapped/where it would be in the priority list but I think we should track this problem & look into it if the tracker behaves as you describe.
Unfortunately I can’t think of a good workaround for it short of manually instrumenting listeners (which is probably not an easy one), but I’ll mull it over and let you know if I think of something.
@Colm sure thing, I’ll submit an issue a bit later and thanks for the note