1247402 - NS_ERROR_MALFORMED_URI with custom about pages in e10s

Status: RESOLVED WORKSFORME

(Firefox :: Extension Compatibility, defect)

Description

[Paul Heil]

Attachment: [e-mail]

User Agent: Mozilla/5.0 (Windows NT 6.1; rv:45.0) Gecko/20100101 Firefox/45.0
Build ID: 20160208194709

Steps to reproduce:

Install test case extension
Click toolbar icon to open demo tab (pinned)




Actual results:

Pinned tab produces "The address isn't valid" error page with this error in console.

NS_ERROR_MALFORMED_URI: Component returned failure code: 0x804b000a (NS_ERROR_MALFORMED_URI) [nsIWebNavigation.loadURIWithOptions] browser-child.js:293:0


Expected results:

The tab should have opened and loaded the content "resource://AboutURLBug-at-testcase-dot-com/data/unicorn.html"

Notes:  Reloading doesn't appear to do anything, but activating the address bar and hitting enter will generate the error again.  By manually typing "about:unicorn" the page will load correctly.  For some reason the testcase is not "working" exactly the same in 45, so I marked as 46 since it's showing the error without an additional error.

Comment 1

[YF (Yang)]

I see the situation in 47.0a1 (2016-02-10).


isPinned is not a necessary condition.
Works fine if changed as url: "about:config", in index.js.
Works fine for e10s off.

Comment 2

[Luís Miguel [:quicksaver] (not reading bugmail)]

FWIW this is the same as bug 1215793. The about: handler is only registered in the chrome process, but because of the URI_CAN_LOAD_IN_CHILD flag, it tries to load it in the child process and fails because it's not registered there. Simplest solution on the add-on side is to also register it in the child process as explained in bug 1215793 comment 7.

Leaving it open though because I don't know how much SDK-related that actually is, so I can't tell if this fix should be on the add-on side or in the SDK itself.

Comment 3

[:shell escalante]

there is an e10s friendly solution - listed in comment 2 if the add-on wants to adopt it