Closed Bug 410499 Opened 17 years ago Closed 17 years ago

Cannot add an opensearch engine with an accent in the title

Categories

(Firefox :: Search, defect)

x86
Windows XP
defect
Not set
minor

Tracking

()

VERIFIED DUPLICATE of bug 357830

People

(Reporter: dodot63, Unassigned)

References

()

Details

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; fr; rv:1.8.1.11) Gecko/20071127 Firefox/2.0.0.11
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; fr; rv:1.8.1.11) Gecko/20071127 Firefox/2.0.0.11

When I'm trying to add a search engine in the search toolbar, if there is an accent in the opensearch plugin title, it won't work.

[Exception... "'Failure' when calling method: [nsIStreamListener::onStopRequest]"  nsresult: "0x80004005 (NS_ERROR_FAILURE)"  location: "<unknown>"  data: no]

It looks stupid, but the 0x80004005 makes me think of an ActiveX error...

Reproducible: Always

Steps to Reproduce:
Try to install a search engine with an accent in the title, for example:
http://www.searchplugins.net/pluginlist.aspx?q=t%E9l%E9charger+logiciels+gratuits&mode=exact
Actual Results:  
Nothing happens, an error is listed in the Error console when the config option browser.search.log is activated.

Expected Results:  
Dialog box asking for confirmation, and search engine installation

I am behind a proxy, I couldn't test with a direct connection for now.
Will be fixed in Firefox 3.
Status: UNCONFIRMED → RESOLVED
Closed: 17 years ago
Resolution: --- → DUPLICATE
Status: RESOLVED → VERIFIED
OK thanks for this fast verification
It'd be great if you could verify the fix in Firefox Beta 2, if you're OK with trying out beta software. The beta is currently available at http://www.mozilla.com/en-US/firefox/all-beta.html . I've verified that the example you gave does work for me, but extra verification doesn't hurt :)
I confirm, fixed. Thanks.
Resolution: DUPLICATE → FIXED
Status: VERIFIED → RESOLVED
Closed: 17 years ago17 years ago
Resolution: FIXED → DUPLICATE
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.