Closed
Bug 1281882
(webext-port-google-hangouts)
Opened 8 years ago
Closed 8 years ago
Enable Google Hangout Chrome extension to work with Firefox
Categories
(WebExtensions :: Compatibility, defect, P5)
WebExtensions
Compatibility
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: mattw, Unassigned)
References
Details
(Whiteboard: [popular chrome extensions]triaged)
Chrome store link: https://chrome.google.com/webstore/detail/google-hangouts/nckgahadagoaajjgafhacjanaoiihapd?hl=en
Firefox testing link: https://addons.allizom.org/en-US/firefox/addon/google-hangout-ica-test/
Reporter | ||
Updated•8 years ago
|
No longer depends on: webext-port-pin-it-button
Comment 1•8 years ago
|
||
Having grepped the full source code, here is a list of missing APIs:
- runtime.onUpdateAvailable
- chrome.idle
- runtime.onMessageExternal (bug 1258360)
Comment 2•8 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•8 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•8 years ago
|
Component: WebExtensions: Untriaged → WebExtensions: Compatibility
Priority: -- → P5
Comment 4•8 years ago
|
||
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•8 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•8 years 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
Closed: 8 years ago
Resolution: --- → FIXED
Updated•6 years ago
|
Product: Toolkit → WebExtensions
You need to log in
before you can comment on or make changes to this bug.
Description
•