The Triage Page is the third and final stage of a Lens diagnosis. It opens in a full browser tab when you click “See full detail” in Fight View. It contains everything from the popup, plus the full context you’d need to either fix the problem yourself or hand it to a developer with nothing left to explain.
How to get there #
Run a diagnosis from the popup. In Fight View, click See full detail. A new tab opens with the Triage Page. The popup resets to its idle state. The Triage Page has everything you need from that point forward.
What the page shows #
The element and screenshot #
The element you diagnosed, cropped from the page, so you can confirm you’re looking at the right thing before acting on the diagnosis.
The verdict #
A plain-language summary of what’s happening and why. This is the same classification the popup Fight View showed, written out in full.
The fight panel #
The full winner and loser breakdown for the property you selected. Same as Fight View, but with no truncation: full selectors, full source paths, full loss reasons.
The override prescription #
When Lens can generate a safe fix, the prescription appears with 3 tabs:
- Base: the narrowest selector that beats the conflict.
- Scoped: prefixed with the current page’s body class, for when the base selector matches more elements than you intend to change.
- Variable update: when the winning value is set via a CSS Variable, this tab gives you the rule that updates the variable at its definition point rather than overriding the resolved value.
The “Where styles come from” panel #
A breakdown of every active CSS property on the element, the rule responsible for each one, and where that rule originated. This is the full CSS origin picture, not just the property you diagnosed.
The developer handoff section #
A pre-written message and the capture file download button. The message contains the specific conflict, what’s winning and why, and everything a developer needs to write a fix without asking follow-up questions. Attach the capture file and send. The capture file download button appears here on the Triage Page, not in the popup.
The feedback form #
If the diagnosis doesn’t match what you’re seeing, submit the feedback form. It flags the session for review.
When to use the Triage Page vs. stopping at Fight View #
If Fight View shows an override prescription and it’s clear what to do, you don’t need the Triage Page. Copy the CSS and paste it in.
Go to the Triage Page when: the override isn’t obvious from Fight View alone, the problem turns out to involve ancestor constraints that aren’t shown in the popup, the triage route is developer handoff and you need the capture file and pre-written message, or you want the scoped or variable variant of the prescription.