Closed
Bug 584864
Opened 14 years ago
Closed 14 years ago
MessageManager's LoadFrameScript runs in Chrome windows
Categories
(Core :: IPC, defect)
Core
IPC
Tracking
()
RESOLVED
FIXED
People
(Reporter: azakai, Assigned: azakai)
References
Details
Attachments
(1 file, 1 obsolete file)
626 bytes,
patch
|
smaug
:
review+
|
Details | Diff | Splinter Review |
If LoadFrameScript is called (see e.g. the patch in bug 550936) in Firefox, then since Firefox creates 4 DocShells for the first window, the frame script is actually loaded 4 times - once in the content window, and once for each of the 3 chrome windows.
This leads to noticeable slowdowns (see discussion in bug 550936). In some cases we would only want the script to be loaded in one type of window - content or chrome. So adding an option for the script to only be loaded in one type would be nice.
Assignee | ||
Updated•14 years ago
|
Summary: Let MessageManager's LoadFrameScript specify Chrome and/or Content → MessageManager's LoadFrameScript runs in Chrome windows
Assignee | ||
Comment 1•14 years ago
|
||
Patch to restore the code that made this work ok (chrome windows are not called), that was lost in a merge at some point.
Attachment #463334 -
Flags: review?(Olli.Pettay)
Comment 2•14 years ago
|
||
Comment on attachment 463334 [details] [diff] [review]
Patch
I'll land this tomorrow.
Attachment #463334 -
Flags: review?(Olli.Pettay) → review+
Comment 3•14 years ago
|
||
...unless someone lands it before :)
Comment 4•14 years ago
|
||
Comment on attachment 463334 [details] [diff] [review]
Patch
Oops, approval is needed.
This patch adds back code which was lost in some
e10s->m-c or m-c->e10s merge.
Attachment #463334 -
Flags: approval2.0?
Updated•14 years ago
|
Assignee: nobody → azakai
Assignee | ||
Comment 5•14 years ago
|
||
This is needed for bug 550936, which is blocking2.0 beta4+ and blocking-fennec 2.0a1+.
blocking2.0: --- → ?
tracking-fennec: --- → ?
Updated•14 years ago
|
Attachment #463334 -
Flags: approval2.0? → approval2.0+
Updated•14 years ago
|
tracking-fennec: ? → 2.0a1+
Comment 6•14 years ago
|
||
I'll push this once my build is ready.
Comment 7•14 years ago
|
||
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
Comment 8•14 years ago
|
||
This patch breaks loading IPC web pages in Fennec (see bug 585606)
Comment 9•14 years ago
|
||
Backed out to fix the regression:
http://hg.mozilla.org/mozilla-central/rev/25a4b29f243b
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Comment 10•14 years ago
|
||
Uh.
We really need some IPC mochitests.
The fix should be.
if (!mIsTopLevelContent && !mRemoteFrame) {
return;
}
Could someone with e10s-fennec verify that it works.
Comment 11•14 years ago
|
||
Or actually the E10s setup in frameloader is just a bit wrong,
since it doesn't set mIsTopLevelContent.
But comment 10 should be enough still.
Comment 12•14 years ago
|
||
(In reply to comment #10)
> Uh.
>
> We really need some IPC mochitests.
>
> The fix should be.
> if (!mIsTopLevelContent && !mRemoteFrame) {
> return;
> }
> Could someone with e10s-fennec verify that it works.
I tested in e10s-fennec. This does in fact work.
Comment 13•14 years ago
|
||
New patch. Tested and confirmed that it works for Fennec.
Attachment #463334 -
Attachment is obsolete: true
Attachment #464081 -
Flags: review?(Olli.Pettay)
Updated•14 years ago
|
Attachment #464081 -
Flags: review?(Olli.Pettay) → review+
Comment 14•14 years ago
|
||
Status: REOPENED → RESOLVED
Closed: 14 years ago → 14 years ago
Resolution: --- → FIXED
Comment 15•14 years ago
|
||
/builds/slave/comm-central-trunk-macosx/build/mozilla/content/base/src/nsFrameLoader.cpp:1892: error: 'mRemoteFrame' was not declared in this scope
make[8]: *** [nsFrameLoader.o] Error 1
http://tinderbox.mozilla.org/showlog.cgi?log=Thunderbird/1281455252.1281455917.13884.gz
Comment 16•14 years ago
|
||
Uh, we need ifdef MOZ_IPC.
Comment 17•14 years ago
|
||
Smaug - Do we need MOZ_IPC and non MOZ_IPC cases?
#ifdef MOZ_IPC
if (!mIsTopLevelContent && !mRemoteFrame) {
return;
}
#else
if (!mIsTopLevelContent) {
return;
}
#endif
Like that?
Comment 18•14 years ago
|
||
The fix for this landed already, I think.
Comment 19•14 years ago
|
||
http://hg.mozilla.org/mozilla-central/rev/e5a5061b99d1
Hopefully it works
Updated•14 years ago
|
blocking2.0: ? → final+
You need to log in
before you can comment on or make changes to this bug.
Description
•