You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit cfecdb8
Browse filesBrowse the repository at this point in the historyBrowse files
feat(browser-bridge): put the installation key in a dialog that knows the extension's page
The key was spread across three places: a fingerprint in the row's description,
the key in a field that only existed while the page stayed open, and a hint
telling the person to find the extension's options page by hand. The person
had to match a key to a browser by reading both sides.
It is now one dialog. The fingerprint the extension's page shows back, the key
itself, a copy action, and a link to the extension's own options page — the
page the key is pasted on — beside them. The link opens in a new tab because
the person has to paste into the page it opens and come back to the dialog for
the copy; the dialog is where the pairing happens.
The host cannot always name that page, and it does not pretend to. The
extension's id is the one its origin carries, so the host knows it only for an
extension it has seen: the live session first, then the identities this host
has proved, then the ones an operator configured — the last two only when
there is exactly one of them, because a page named for the wrong extension is
worse than no page at all. With no known identity the dialog says so and
gives the manual path instead of a link that could open the wrong extension.
Both actions the person takes here — the key button and the extension package
download — now use the shared button contract, so they read like every other
button in Settings instead of like a page of their own.
The published inventory regains the three source files the extension package
commit added: they were committed but never recorded, so the source gate could
not have passed for them. It also records three paths that are still being
written elsewhere in this working tree, because the inventory describes the
tree it is generated from.
0 commit comments