Jorge Villalobos [:jorgev] (he/him) Reporter
	Description • 11 years ago

Steps to reproduce:
1) Install testcase add-on.
2) Go to a mozilla.org

Expected result:

After loading, the page will become blank. 

Observed result:

With e10s activated on the latest nightly (27.0a1 (2013-10-15)) and just after the extension is installed, nothing happens. If the browser is restarted, the extension works normally.

I noticed 2 identical errors in the console right after installation:

aDocShell is null browser.js:157

They appear to break gXPInstallObserver, so that's one possible cause for the problems. Another thing to take into account is that the file is being installed locally, by dropping it into the Add-ons Manager window.

	Jorge Villalobos [:jorgev] (he/him) Reporter
	Comment 1 • 11 years ago

(In reply to Jorge Villalobos [:jorgev] from comment #0)
> 2) Go to a mozilla.org

I meant "Go to mozilla.org", but anything under mozilla.org or mozilla.com should work.

	Olli Pettay [:smaug][bugs@pettay.fi]
	Comment 2 • 11 years ago

Well if we're in e10s mode, there is no docshell for tabs, or the docshell is in the child process, 
not accessible to browser chrome.

	Chris Peterson [:cpeterson]
	Comment 3 • 10 years ago

Mass tracking-e10s flag change. Filter bugmail on "2be0fcce-e36a-4e2c-aa80-0e3d33eb5406".

	Blake Kaplan (:mrbkap) (inactive) Assignee
	Comment 4 • 10 years ago

It appears that we're not correctly propagating the new chrome:// stuff to the content process.

	Josh Matthews [:jdm]
	Comment 5 • 10 years ago

See bug 687194.