Can’t authorize extension in Firefox for Android

[da2x]

(We’ve discussed this before over email, but I wanted to add a public issue for it as well.)

Differences between desktop and Android extension API. Specifically, the browser.history and browser.windows are unavailable on Firefox for Android. The Flattr extension uses these APIs without testing whether they’re available or not. (This will also cause issues for a Microsoft Edge port.)

Idea: when installed, the extension could display a message suggesting to uninstall the extension and enable Firefox Sync with History Sync on a desktop computer as well as on the mobile device. At least as a temporary work-around.

[ThomasGreiner]

Since we don't support Firefox Mobile at this point, there are a couple of areas we'd need to tackle, as you outlined already, to change that:

• Fix authentication issue (see bug 1408996)
• API support
• Adapt UI for smaller screens
• Adapt icon popup UI for browsers which don't support browser actions popups

Note that the browser.history API would likely not be necessary for Firefox Mobile since its main purpose is to get notified of visits from browsers that are linked to the same account and on which the extension cannot be installed (i.e. Chrome Mobile). We're also trying to avoid that a single visit can cause the creation of the same flattr across multiple devices.