Search bar is ignoring language listed in opensearch definition

UNCONFIRMED
Unassigned

Status

()

defect
P3
normal
Rank:
35
UNCONFIRMED
4 years ago
4 years ago

People

(Reporter: bonbons, Unassigned)

Tracking

36 Branch
x86
Linux
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [fxsearch])

User Agent: Mozilla/5.0 (X11; Linux i686; rv:36.0) Gecko/20100101 Firefox/36.0
Build ID: 20150301125210

Steps to reproduce:

I registered a search engine to search bar using the "Add {ShortName}" option in the search bar menu.

The definition of the engine (URLs for documentation purpose):
<?xml version="1.0" encoding="UTF-8"?>
<OpenSearchDescription xmlns="http://a9.com/-/spec/opensearch/1.1/">
  <ShortName>MyEngine</ShortName>
  <Description>MyEngine search tool</Description>
  <Url type="text/html" template="http://www.eample.com/{language}/search.html?keywords={searchTerms}" />
  <Url type="application/atom+xml" template="http://www.example.com/{language}/search.xml?keywords={searchTerms}&amp;count={count}&amp;page={startPage}" />
  <Url type="application/opensearchdescription+xml" rel="self" template="http://www.example.com/opensearch.html" />
  <Image>http://www.example.com/favicon.ico</Image>
  <Query role="example" searchTerms="example" />
  <SyndicationRight>limited</SyndicationRight>
  <Language>fr</Language>
  <Language>en</Language>
  <Language>nl</Language>
  <Language>de</Language>
  <InputEncoding>utf-8</InputEncoding>
  <OutputEncoding>utf-8</OutputEncoding>
</OpenSearchDescription>

Configured languages in Preferences: en, fr, de


Actual results:

When searching with the added engine Firefox is replacing {language} in the Url@template with the UI language (en-US) which is not even listed as supported by the engine.


Expected results:

Firefox should have chosen 'en' instead of 'en-US' or even better offered the option to select the language in the search bar popup from those supported by the engine.
Component: Untriaged → Search
Priority: -- → P3
Whiteboard: [fxsearch]
Rank: 35
You need to log in before you can comment on or make changes to this bug.