🐛 Treating synthetic PointerEvent on removeVanillaNestedFields

[lenilsonjr]

Hi there 👋

This is a great library, thanks for maintaining it!

I faced the same issue as #47 when using vanilla-nested with Turbo, and pointing my gem to the main branch of the repo solved it (kudos for the fix).

However, it seems that the changes here introduced a edge-case error that I could trace to removeVanillaNestedFields receiving a synthetic PointerEvent instead of the expected element directly, under some circumstances. I added a small conditional with this PR to deal with both cases.

It seems that the synthetic event is only sent when removing nested fields added by clicking on the link generated by link_to_add_nested.

This may not be the best fix (and I may not understand the underlying reason this is happening), but I thought I'd send this PR and document the fix and the error anyway.

Tested on Chrome.

Thanks!

[arielj]

thank you! I'll try to review the fix today or tomorrow, after that I'll make a new relase, thanks!

[arielj]

thanks! after checking this I found the actual root cause of the problem so now it should always receive an HTMLElement

For reference: 166835d

I'll make a new release in a moment