Open
Bug 936776
Opened 11 years ago
Updated 2 years ago
chrome-document-global-created not fired when calling loadURI() after swapDocShell() with uninitialized browser
Categories
(Core :: DOM: Core & HTML, defect, P5)
Tracking
()
UNCONFIRMED
People
(Reporter: piotrekrom7, Unassigned)
Details
Attachments
(1 file)
2.99 KB,
application/x-javascript
|
Details |
User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:25.0) Gecko/20100101 Firefox/25.0 (Beta/Release) Build ID: 20131025151332 Steps to reproduce: 1. Run the attached js in Browser Console 2. Type init(); (setting up {chrome,content}-document-global-created notifications for tracing them) 3. Open sidebar with e.g. Bookmarks. 4. Type runTest(); Then following steps will be run: 4.1 Creating new <browser> with src="about:blank" and it will be attached to DOM 4.2 Calling swapDocShells for current sidebar and the new <browser>. 4.3 Calling loadURI() in sidebar. Actual results: The "chrome-document-global-created" notification has been fired only once i.a. for the new <browser> element, in console you can see: chrome-document-global-created before load: '', <browser>.id='__emptySidebar' ater load: 'about:config', <browser>.id='sidebar' When a content loads it turns out that subject window obj is the window loaded in sidebar by loadURI. Expected results: I expected that when I call loadURI("about:config") in sidebar browser, a chrome-document-global-created notification will be fired while subject window will be equal to sidebarBrowser.contentWindow.
Comment 1•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
Assignee | ||
Updated•5 years ago
|
Component: DOM → DOM: Core & HTML
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•