`turbolinks:load` events persist across page loads
turbolinks:load
events stack and are called again after navigating away from the page that set them:
- Go to a project/group page with a user selection dropdown, which has a
turbolinks:load
event in its script. As expected, the event is called. - Navigate to another page: the event is executed again (and it cannot find its elements so it throws an exception, breaking the event loop (not sure if that's actually the case, but all subsequent load events don't execute))
This is the case everywhere turbolinks:load
events are used (e.g. !710 (merged))