1068824 - [e10s] duckduckgo's "use in firefox" button fails

Status: RESOLVED DUPLICATE of bug 1068186

(Firefox :: General, defect)

Description

[Barbara Miller (:galgeek)]

User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:32.0) Gecko/20100101 Firefox/32.0
Build ID: 20140911151253

Steps to reproduce:

open duckduckgo.com
click "Use in Firefox" button
in resulting popup, click green OK
a new, empty tab opens. duckduckgo is not added to the search engine list.


Actual results:

(see above)


Expected results:

current "shipping" and beta Firefox show a dialog box allowing you to add duckduckgo to Firefox's search engine list and optionally make it default.

Comment 1

[Barbara Miller (:galgeek)]

The User Agent details in my original post are for the browser where I'm using bugzilla.

The buildid of Nightly where I found this bug is 20140917030202

Comment 2

[Alice0775 White]

Confirmed, I can reproduce the problem in e10s Nightly, but not non-e10s.

Comment 3

[Justin Dolske [:Dolske]]

Dupe of bug 1068186? Do you see the same error message that bug reports?

Comment 4

[Alice0775 White]

(In reply to Justin Dolske [:Dolske] from comment #3)
> Dupe of bug 1068186? Do you see the same error message that bug reports?

No it is not same. the Browser consoloe says:

TypeError: win is null nsSidebar.js:89

NS_ERROR_UNEXPECTED:  d1677.js:70

Comment 6

[Dave Townsend [:mossop]]

(In reply to Alice0775 White from comment #4)
> (In reply to Justin Dolske [:Dolske] from comment #3)
> > Dupe of bug 1068186? Do you see the same error message that bug reports?
> 
> No it is not same. the Browser consoloe says:
> 
> TypeError: win is null nsSidebar.js:89
> 
> NS_ERROR_UNEXPECTED:  d1677.js:70

Those look like the same error messages

Comment 7

[Brian S]

Hey, is there anything we (DuckDuckGo) can do to help with this?

It seems like the call to window.external.AddSearchProvider() is throwing this error?

I can reproduce in the console:

window.external.AddSearchProvider("https://duckduckgo.com/opensearch.xml")
[Exception... "Unexpected error"  nsresult: "0x8000ffff (NS_ERROR_UNEXPECTED)"  location: "JS frame :: debugger eval code :: <TOP_LEVEL> :: line 1"  data: no]

Comment 8

[Justin Dolske [:Dolske]]

Not really, this is a bug in Firefox's new E10S (multiprocess) mode, and requires a fix in Firefox.

Note that since it's only a bug with E10S enabled, and we're not enabling that mode by default yet, the vast majority of users won't be affected by it. Basically it's only an issue for users on pre-release versions of Firefox who have enabled E10S.

Comment 9

[Brian S]

Okay, thanks for the update!