Surfaces
The menu, the popup and the trace.
Three surfaces read the same state. The menu is the full report, the popup is the same state at a glance, and the trace is the rolling history of every stage.
Runs on any checkout page you already open. Reversible in one deploy.
How it works
Open the menu
The menu page shows the hero, the state tiles, the live panel, the switches and the trace.
Open the popup
The popup shows stage and relay tiles beside the last run, so the outcome is readable in one glance.
Read the trace
Detect, authenticate, poll, probe and relay are recorded with their HTTP codes, newest at the bottom.
Copy the snapshot
Copy snapshot puts the current state on the clipboard for a report or a ticket.
All three repaint the moment storage changes, so a finished run appears without a refresh.
Header buttons work
Overview, State, Switches and Trace jump to their section and set the active state, so the menu behaves like a page rather than a list.
- Overview
- State
- Switches
- Trace
State survives the tab
The last run and the trace are kept in storage, so the menu still shows the outcome after the checkout tab closes.
- Persisted last result
- Rolling trace
- Live repaint
Questions about this one.
More on the full FAQ, or write to [email protected].
01Why do the surfaces repaint?
Because the menu and popup listen to storage changes, so a finished run appears without pressing refresh.
02Where is the trace stored?
In extension storage, alongside the last result, so it survives a tab close.
03Can I clear it?
Yes. Clear trace empties the history, and Reset tab state clears the per-tab state.
Surfaces
Read the run without a refresh.
The menu, popup and trace all repaint from the same stored state, so the outcome is visible the moment it settles.
- Live repaint
- Persisted state
- Copy snapshot