chrome-document-global-created not fired when calling loadURI() after swapDocShell() with uninitialized browser

RESOLVED INACTIVE

Status

()

Core
DOM
RESOLVED INACTIVE
5 years ago
2 days ago

People

(Reporter: piotrekrom7, Unassigned)

Tracking

25 Branch
x86_64
Windows 7
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(1 attachment)

2.99 KB, application/x-javascript
Details
(Reporter)

Description

5 years ago
Created attachment 829714 [details]
domwinobs-test-2.js

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.

Updated

5 years ago
Component: Untriaged → DOM
Product: Firefox → Core

Comment 1

2 days ago
Per policy at https://wiki.mozilla.org/Bug_Triage/Projects/Bug_Handling/Bug_Husbandry#Inactive_Bugs. If this bug is not an enhancement request or a bug not present in a supported release of Firefox, then it may be reopened.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 2 days ago
Resolution: --- → INACTIVE
You need to log in before you can comment on or make changes to this bug.