Closed Bug 1124527 Opened 8 years ago Closed 8 years ago

[e10s] Unable to access OpenH264 license from add-on manager

Categories

(Firefox :: General, defect)

defect
Not set
normal

Tracking

()

RESOLVED DUPLICATE of bug 1047603
Tracking Status
e10s ? ---

People

(Reporter: spohl, Unassigned)

References

(Blocks 2 open bugs)

Details

Steps:
1. Tools > Add-ons
2. For OpenH264, click on "More" or the Preferences button
3. Click on "License information".

Actual:
Spinning progress indicator, followed by blank page.

Expected:
License displays.

This does not occur when the add-on manager is launched in a non-e10s window.
This e10s bug will also affect EME CDM license links.
Blocks: fxe10s, EME
tracking-e10s: --- → ?
Hardware: x86 → All
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → DUPLICATE
Mike, are you convinced that this is the same issue as bug 1114299? I, for one, am not able to reproduce the problem with the test case in bug 1114299. After clicking the link, https://www.mozilla.org/en-US/ is loaded correctly and the browser chrome looks correct. However, clicking the link to the license file in the OpenH264 preference pane in the addon manager gives me a spinning wheel, followed by a blank page. The license file never loads. Could the difference be that we're trying to load a "chrome://" URL here?
Flags: needinfo?(mconley)
I guess I should add that I tested this on OSX 10.10.2 with a local build based off of changeset 3bf7ed413e87 [1].

[1] https://hg.mozilla.org/mozilla-central/rev/3bf7ed413e87
(In reply to Stephen Pohl [:spohl] from comment #3)
> Mike, are you convinced that this is the same issue as bug 1114299? I, for
> one, am not able to reproduce the problem with the test case in bug 1114299.
> After clicking the link, https://www.mozilla.org/en-US/ is loaded correctly
> and the browser chrome looks correct. However, clicking the link to the
> license file in the OpenH264 preference pane in the addon manager gives me a
> spinning wheel, followed by a blank page. The license file never loads.
> Could the difference be that we're trying to load a "chrome://" URL here?

Gah, sorry - sloppily duped. I meant to dupe it to bug 1047603. Thanks for the heads up. :)
Flags: needinfo?(mconley)
You need to log in before you can comment on or make changes to this bug.