Thansk for your work on this gem!

To start, I definitely understand that activeadmin is not actively looking to switch away from jQuery. That would be a massive effort. However, I think I've run into a particular problem that would justify moving away from jQuery events.

In our app, we have a guideline in place to avoid jQuery unless necessary. We wanted to add some JS code to listen for the has_many_remove:before event, so we added:

document.addEventListener("has_many_remove:before", (ev) => { doSomething() })

however, that's never triggered. This does get triggered, though:

$(document).on("has_many_remove:before", (ev) => { doSomething() })

The reason is that has_many.js is calling jQuery's .trigger function here:

If we were able to switch all of the trigger calls to dispatchEvent, we could have both jQuery AND native event listeners to fire. However, because the trigger calls pass in arguments representing the item to remove and the parent element, I believe this would be a breaking change. Native events would have to store those elements in the event data's detail property, while jQuery passes those elements as arguments to the listener function:

document.addEventListener("has_many_remove:before", (ev) => { doSomething(ev.detail.toRemove, ev.detail.parent) })
// vs.
$(document).on("has_many_remove:before", (ev, toRemove, parent) => { doSomething(toRemove, parent) })

I'm not sure if there's a way to make this a non breaking change (probably not?).

Would AA be willing to make this breaking change?