mozilla/browserid — Issue #601: build pagemod-ready API
Author: benadida
Created: 2011-11-18 00:58:10+00:00
State: open
Labels: ★★★★

we need to expose a JS API in the BrowserID dialog that lets chrome-level apps do what they need to do, including fully control BrowserID functions. This API, if well defined, can then be stable.

Specifically:

* navigator.id.channel can be defined by the chrome to provide an alternative message-passing channel. This is already done and should stay.

* navigator.id.internal.getSilent(origin, email, {options}, callback): generate an assertion for the given origin and email, with options, and the callback to be called with the assertion.

* navigator.id.internal.setPersistent(origin, email): set the persistent login for this email address at this origin.

The first (navigator.id.channel) should be exposed by the chrome to browserid.org, while the other two (internal.*) should be exposed by the browserid.org to the chrome.