Closed
Bug 1241023
Opened 9 years ago
Closed 9 years ago
[ e10s] html content (hosted in xul iframe) can not load flash swf
Categories
(Core Graveyard :: Plug-ins, defect)
Tracking
(e10s?, firefox42 unaffected, firefox43 unaffected, firefox44 unaffected, firefox45- unaffected, firefox46- unaffected, firefox47 fixed)
RESOLVED
DUPLICATE
of bug 1237402
Tracking | Status | |
---|---|---|
e10s | ? | --- |
firefox42 | --- | unaffected |
firefox43 | --- | unaffected |
firefox44 | --- | unaffected |
firefox45 | - | unaffected |
firefox46 | - | unaffected |
firefox47 | --- | fixed |
People
(Reporter: any_trade, Unassigned)
References
Details
(Keywords: regression, testcase)
User Agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:43.0) Gecko/20100101 Firefox/43.0
Build ID: 20160105164030
Steps to reproduce:
// My addon js:
var wm = Components.classes["@mozilla.org/appshell/window-mediator;1"]
.getService(Components.interfaces.nsIWindowMediator);
var wins = wm.getEnumerator("navigator:browser");
var xdoc;
try {
while (wins.hasMoreElements()) {
let win = wins.getNext().QueryInterface(Components.interfaces.nsIDOMWindow);
if (win) {
xdoc = win.document;
break;
}
}
} catch(e) { }
if(xdoc) {
let f = xdoc.createElement("iframe");
f.setAttribute("id", "xul-iframe-flash-test");
f.setAttribute("type", "content");
f.setAttribute("height", "320");
f.setAttribute("collapsed", "false");
let xMainWin = xdoc.getElementById("main-window");
if (xMainWin) {
xMainWin.appendChild(f);
f.webNavigation.allowAuth = true;
f.webNavigation.allowImages = true;
f.webNavigation.allowJavascript = true;
f.webNavigation.allowMetaRedirects = true;
f.webNavigation.allowPlugins = true;
f.webNavigation.allowSubframes = true;
f.setAttribute("src", "http://tv.adobe.com/watch/learn-premiere-elements-7/mixing-audio/");
}
}
Actual results:
The flash swf can not load and play.
Expected results:
The flash swf can load and play.
Reporter | ||
Updated•9 years ago
|
OS: Unspecified → Windows 7
Hardware: Unspecified → x86_64
Could you attach your add-on as xpi (or a simple version) showing the issue, please.
Flags: needinfo?(any_trade)
Keywords: testcase-wanted
Reporter | ||
Comment 2•9 years ago
|
||
(In reply to Loic from comment #1)
> Could you attach your add-on as xpi (or a simple version) showing the issue,
> please.
Thanks for your reply first.
My addon is under code writing, so it is no xpi yet. You can install "tiny-javascript-debugger" (https://addons.mozilla.org/en-US/firefox/addon/tiny-javascript-debugger/) and copy above js code then paste them into the Scratchpad box to reproduce the bug.
Thanks
Flags: needinfo?(any_trade)
I see the in e10s-on Nightly, not in e10s-off Nightly.
Blocks: e10s
Status: UNCONFIRMED → NEW
Component: Untriaged → Plug-ins
Ever confirmed: true
Keywords: testcase-wanted → testcase
OS: Windows 7 → All
Product: Firefox → Core
Hardware: x86_64 → All
Whiteboard: [DUPEME]
In fact, no need of this add-on, turning on "Enable browser chrome and add-on debugging toolboxes" in the settings of the devtools and running the JS code in Scratchpad is enough to reproduce the issue with e10s enabled.
Regression range:
https://hg.mozilla.org/integration/mozilla-inbound/pushloghtml?fromchange=4bae26d5e06f263cfbd03ffa6adbcec06da18abf&tochange=19d97c221555b28afdb7a0d987e7a4f910d6a2f3
Brad Lassey — bug 1155976 - Loading plugins in a non-e10s window hangs the browser on Mac r=jimm
Blocks: 1155976
status-firefox42:
--- → affected
status-firefox43:
--- → affected
status-firefox44:
--- → affected
status-firefox45:
--- → affected
status-firefox46:
--- → affected
tracking-firefox45:
--- → ?
tracking-firefox46:
--- → ?
Flags: needinfo?(blassey.bugs)
Keywords: regression
Summary: [FF45.0a2-en_US-win64, e10s enabled] html content (hosted in xul iframe) can not load flash swf → [ e10s] html content (hosted in xul iframe) can not load flash swf
Whiteboard: [DUPEME]
Version: 45 Branch → 40 Branch
Maybe a dupe of bug 1158788.
Reporter | ||
Comment 6•9 years ago
|
||
(In reply to Loic from comment #4)
> In fact, no need of this add-on, turning on "Enable browser chrome and
> add-on debugging toolboxes" in the settings of the devtools and running the
> JS code in Scratchpad is enough to reproduce the issue with e10s enabled.
>
> Regression range:
> https://hg.mozilla.org/integration/mozilla-inbound/
> pushloghtml?fromchange=4bae26d5e06f263cfbd03ffa6adbcec06da18abf&tochange=19d9
> 7c221555b28afdb7a0d987e7a4f910d6a2f3
>
> Brad Lassey — bug 1155976 - Loading plugins in a non-e10s window hangs the
> browser on Mac r=jimm
Thanks for your info about turn on js scratchpad in devtools.
Just try some case in last few minutes.
1. ADD following two lines.
f.setAttribute("messagemanagergroup", "browsers");
f.setAttribute("message", "true");
a)The flash box shows "This plugin is disabled." and X icons instead of purely all grey background.
b)"TypeError: browser.permanentKey is not a non-null... SessionStore.jsm:705..." showed in Browser Console.
2. OPEN a "New non-e10s window" from File menu, in non-e10s window open "http://tv.adobe.com/watch/learn-premiere-elements-7/mixing-audio/" can also produce the same thing I mentioned in 1.
Thanks
Comment 7•9 years ago
|
||
This is intentional, so not a "regression" exactly. Bill is looking for ways to allow web extensions to run plugins in the chrome process (and not in the content process) though.
Flags: needinfo?(blassey.bugs) → needinfo?(wmccloskey)
If addon developers are hitting this issue and we plan to do some work to support this with e10s enabled, maybe track for e10s? Noting that the duplicate bug is marked as wontfix.
tracking-e10s:
--- → ?
Flags: needinfo?(blassey.bugs)
Starting with bug 1237402, you will be able to set a pref, "plugin.load_in_parent_process.<your-plugin-MIME-type>", and your plugin will run in the main process. However, it will not run in the content process. I hope this works for you.
Flags: needinfo?(wmccloskey)
Updated•9 years ago
|
Flags: needinfo?(blassey.bugs)
Updated•9 years ago
|
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → DUPLICATE
Tracking for 46 in bug 1237402.
Updated•9 years ago
|
Updated•3 years ago
|
Product: Core → Core Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•