As an alternative to dispatching the event with a reference to the original, would explicitly preventing the default if event.defaultPrevented serve the same purpose without expanding the surface area of the CustomEvent.detail?

applicationAllowsFollowingLinkToLocation(link: Element, location: URL, mouseEvent: MouseEvent) {
  const event = this.notifyApplicationAfterClickingLinkToLocation(link, location)

  if (event.defaultPrevented) {
    mouseEvent.preventDefault()
    return false
  } else {
    return true
  }
}

I don't think they are the same behavior. We don't always want to prevent the browser click when preventing turbo:click

the use cases would be:

1. I want to prevent Turbo from navigating and let the browser do it -> prevent turbo:click
2. I want to prevent all navigations -> prevent both events

With that in mind, could we make Frame navigation internally aware of the cancellation?

from my understanding, this is where we trigger the Frame navigation:

this is listening to the turbo:click event, so it should be possible for it to know if the event is defaultPrevented. The problem is that the interceptor runs before any addEventListener I add, so the it always evaluates the event first, and it is never prevented.

maybe we could update

to dispatch another event (if the click isn't prevented) that the LinkInterceptor listens to

@seanpdoyle would adding another internal event make sense here?