Traffic & Event Model

The browser events emitted by loader-based installs and how to observe or intercept traffic safely.

Last reviewed

Traffic & Event Model

Loader-based installs emit browser events with the getuserfeedback: prefix.

Traffic interception

getuserfeedback:traffic fires whenever the loader forwards a public command, telemetry envelope, or app event across the host boundary.

Listeners can:

  • inspect the direction metadata and payload
  • replace event.detail.payload before delivery
  • call event.preventDefault() to veto the payload entirely

Use this carefully. It sits in the middle of command delivery.

Stable host events

The public host event surface includes:

  • getuserfeedback:traffic
  • getuserfeedback:loader:error
  • getuserfeedback:instance:flow:state-changed
  • getuserfeedback:instance:flow:state-changed:instance
  • getuserfeedback:instance:command:settled
  • getuserfeedback:instance:handle:invalidated
  • getuserfeedback:instance:command:unsupported
  • getuserfeedback:instance:open:requested
  • getuserfeedback:instance:error
  • getuserfeedback:instance:app-event

These are the events to build against. Do not invent private navigation or host context events on top of internal runtime behavior.