Closed Bug 169048 Opened 22 years ago Closed 22 years ago

Search: sherlock needs to be able to take the range index search

Categories

(SeaMonkey :: Search, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 149931

People

(Reporter: rchen, Assigned: samir_bugzilla)

Details

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; en-CA; rv:1.0.1) Gecko/20020823 Netscape/7.0
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-CA; rv:1.0.1) Gecko/20020823 Netscape/7.0

Currently the browser only takes one entry as search index in sherlock.  We need
to be able to take two entries as the range indexes for some search engines.  

Reproducible: Always

Steps to Reproduce:
1.
2.
3.
Summary: sherlock need to be able to take the range index search → sherlock needs to be able to take the range index search
Summary: sherlock needs to be able to take the range index search → Search: sherlock needs to be able to take the range index search
rchen, can you explain what you mean with "range index"? Is it something about
the prev/next buttons in the sidebar?
Yes. We encountered some web search comes with "first" and "last" to indicate
the range of the result items.  Currently <inputnext> and <inputprev> only have
one "factor" variable. The initial value is always set to "0" in the program,
which causes it impossible to accommodate the range indexes.  

My suggestion is to add "value" into <inputnext> and <inputprev>. It can be "0"
by default. However we can initialize the value if we want. So we can have 
<inputnext name="start" factor="10">
<inputprev name="start" factor="10">
for the single entry OR 
<inputnext name="first" value="1"  factor="10">
<inputnext name="last"  value="10" factor="10">
<inputprev name="first" value="1"  factor="10">
<inputprev name="last"  value="10" factor="10">
for the two entries.


*** This bug has been marked as a duplicate of 149931 ***
Status: UNCONFIRMED → RESOLVED
Closed: 22 years ago
Resolution: --- → DUPLICATE
Product: Core → SeaMonkey
You need to log in before you can comment on or make changes to this bug.