Browser Extension Connection Check | Entry Page, Permission Prompt, and Device Screen
A browser extension connection check should begin with the entry page, then move to the permission prompt, the app view, and the device screen. The useful question is not whether every browser page should be treated the same, but whether each step belongs to the expected connection path.
Entry page sets the starting point
Start by naming the entry page that opened the extension flow. The browser extension connection FAQ gives a simple way to keep the page source separate from the device response.
Permission prompt belongs to the browser side
A permission prompt is part of the browser environment. Record what permission is being requested, which app view is open, and whether the request matches the task. For general connection context, Ledger connection checks can help separate cable, app state, and prompt type.
Device screen is the confirmation layer
The device screen should be reviewed as its own step. If the browser page and the device screen are describing different tasks, pause and return to the intended entry page before continuing.
Local record closes the check
- Entry page and extension name.
- Permission prompt and app view.
- Device screen wording.
- Next local record before continuing.
For broader app-entry context, Ledger network requirement notes explain how app entry and device prompts stay separate.
