Closed
Bug 575640
Opened 14 years ago
Closed 2 years ago
[e10s] document nsIFrameLoader
Categories
(Core :: DOM: Content Processes, defect, P5)
Core
DOM: Content Processes
Tracking
()
RESOLVED
INVALID
People
(Reporter: dougt, Unassigned)
References
Details
>+++ b/content/base/public/nsIFrameLoader.idl >+ readonly attribute nsIWebProgress webProgress; We should document that this is always available, even in multiprocess situations. We should also document that docShell is NOT always available. >+ * Activate remote frame. >+ * Throws an exception with non-remote frames. >+ */ >+ void activateRemoteFrame(); That needs a lot more documentation. What does "activate" mean, exactly?
Reporter | ||
Comment 1•14 years ago
|
||
There are more methods in this interface that also need documentation
Updated•14 years ago
|
tracking-fennec: --- → ?
Comment 3•14 years ago
|
||
What kind of documentation are we talking about here? - just in the IDL?
Reporter | ||
Comment 4•14 years ago
|
||
yes, just the IDL
Updated•10 years ago
|
tracking-e10s:
--- → +
Updated•10 years ago
|
Updated•10 years ago
|
Component: IPC → DOM: Content Processes
Comment 5•10 years ago
|
||
Sorry for my intrusion but are iframes loaded into a new thread with e10s, or just the tabs? I could not find a single document clearing this out. thanks.
Comment 6•6 years ago
|
||
https://bugzilla.mozilla.org/show_bug.cgi?id=1472046 Move all DOM bugs that haven’t been updated in more than 3 years and has no one currently assigned to P5. If you have questions, please contact :mdaly.
Priority: -- → P5
Comment 7•2 years ago
|
||
Bug 1444143 removed nsIFrameLoader.
Status: NEW → RESOLVED
Closed: 2 years ago
Resolution: --- → INVALID
You need to log in
before you can comment on or make changes to this bug.
Description
•