Open Bug 354950 Opened 14 years ago Updated 5 years ago
Search support doesn't honour 'page Offset' and 'index Offset' attributes of description
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.8.1b2) Gecko/20060601 BonEcho/2.0b2 (Ubuntu-edgy) Build Identifier: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.8.1b2) Gecko/20060601 BonEcho/2.0b2 (Ubuntu-edgy) For OpenSearch, it's possible to define a search engine whose first search result is numbered "0", and first page of search results is numbered "0", too. This is done using the "indexOffset" and "pageOffset" parameters on the Url element of the OpenSearchDescription document. The default for each is "1". Even when the attribute is set in the OpenSearch description, Firefox requests the first search results with startIndex = 1. Reproducible: Always Steps to Reproduce: 1. Create an OpenSearch description with indexOffset = 0. 2. Add the description to Firefox. 3. Do a search. Actual Results: The startIndex parameter is set to 1. Expected Results: The startIndex parameter should be unset or set to 0. Leaving out the startIndex parameter template from the OpenSearch description gives normal functionality. Since Firefox doesn't do paged or indexed searches, it's a moot point, but IWBNI the software would follow the standard.
Status: UNCONFIRMED → NEW
Ever confirmed: true
Yeah, we don't support indexOffset or pageOffset, because when I was implementing the OpenSearch support that parameter wasn't yet finalized.
Assignee: nobody → gavin.sharp
OS: Linux → All
Priority: -- → P3
Hardware: PC → All
Target Milestone: --- → Firefox 3 alpha1
Version: unspecified → Trunk
Target Milestone: Firefox 3 alpha1 → ---
Assignee: gavin.sharp → nobody
Status: ASSIGNED → NEW
Priority: P3 → --
In the renewal MDC, Search engine( http://developer.mozilla.org/@gui/opensearch/description ) have indexOffset attribute set to "0". Then if use this search engine, Search results don't show 1st hit page always.
had this lying around in a tree...
You need to log in before you can comment on or make changes to this bug.