Closed Bug 1059889 Opened 10 years ago Closed 10 years ago

Determine if Garmin Communicator functions in e10s & fix it if not

Categories

(Firefox :: Extension Compatibility, defect)

x86_64
Windows 8
defect
Not set
normal

Tracking

()

RESOLVED WORKSFORME
Tracking Status
e10s + ---
firefox34 --- verified

People

(Reporter: ally, Unassigned)

References

Details

According to amo, this is in the top 25 addons. However it has been broken in single process firefox since February, Bug 972052. Therefore the e10s considerations cannot advance until that is fixed.
tracking-e10s: --- → +
Depends on: 972052
The plugin itself was never broken, but the way how it was usable from an end-user perspective. That means it was hidden and not easily to activate. Given that this feature doesn't exist anymore, there is no problem in using the plugin. I have successfully uploaded records from my Garmin device. Also please be informed that Garmin did a large upgrade lately and introduced Garmin Express. This is an application which runs natively on the machine. Mean the plugin is no longer necessary. Only the old version of the website still requires it.
So, it works with autostart= true?
Flags: needinfo?(hskupin)
That's what I'm saying, correct. But I can only test it on OS X given that I don't have a native Windows system, which would also detect the device via USB. On Linux the plugin is not supported.
Flags: needinfo?(hskupin)
And the only thing I see so far, but which also belongs to Flash, are crashing during shutdown. See bug 1059953.
Ok. I declare this addon not eligible for shim/cpow consideration during the m2 phase.
I was able to get my Mac setup and running with Garmins "classic" mode, which uses the old broswer addon along with Ant Agent. I was able to upload data from device to computer to cloud with on latest Nightly in e10s mode.
Thanks, Tracy! WFM until someone complains. :)
Blocks: e10s-addons
Status: NEW → RESOLVED
Closed: 10 years ago
Component: Untriaged → Extension Compatibility
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.