Bug 1281882 (webext-port-google-hangouts)

Enable Google Hangout Chrome extension to work with Firefox

RESOLVED FIXED

Status

WebExtensions
Compatibility
P5
normal
RESOLVED FIXED
2 years ago
a month ago

People

(Reporter: mattw, Unassigned)

Tracking

(Blocks: 1 bug)

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [popular chrome extensions]triaged)

(Reporter)

Updated

2 years ago
No longer depends on: 1281832
Having grepped the full source code, here is a list of missing APIs:

- runtime.onUpdateAvailable
- chrome.idle
- runtime.onMessageExternal (bug 1258360)
Depends on: 1258360

Comment 2

2 years ago
I get this error when installing from AMO "This add-on could not be installed because it appears to be corrupt" in recent Nightly.

Should I add bug #1313567 in this bug's "Depends on" section?

Comment 3

2 years ago
Bug 1313567 is about the author property and this has no such property in the manifest.

If you want to install an add-on from the add-ons stage server (note the allizom.org domain), then you need to go to about:config and turn off the signature check (xpinstall.signatures.required). Once I do that this add-on installs just fine, but the browser action doesn't work.
Depends on: 1279012

Updated

2 years ago
Component: WebExtensions: Untriaged → WebExtensions: Compatibility
Priority: -- → P5
I strongly suspect that this won't work even if we do add support for all of these things, given that it relies on Hangouts knowing about the extension. onMessageExternal certainly won't work, even if Hangouts did try to use it in non-Chrome browsers, since the extension ID/URL would not be the same.

Comment 5

2 years ago
I will never disable signature check. I will sign it myself if I need to.

Thank you for the extra info.

Comment 6

a year ago
There are no blocking bugs left on this, so I'm going to mark this as resolved fixed in that it should now be possible based on the APIs.
Status: NEW → RESOLVED
Last Resolved: a year ago
Resolution: --- → FIXED

Updated

a month ago
Product: Toolkit → WebExtensions
You need to log in before you can comment on or make changes to this bug.