Closed Bug 285539 Opened 20 years ago Closed 20 years ago

Sidebar Next Previous step incorrectly

Categories

(SeaMonkey :: Search, defect)

x86
Windows XP
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 150337

People

(Reporter: dave, Unassigned)

Details

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8b) Gecko/20050217
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8b) Gecko/20050217

The sidebar next/previous buttons cause sites to step through multiple pages at
the wrong rates.

Reproducible: Always

Steps to Reproduce:
1.f9, show sidebar
2.search for 'google' using Google
3.Press sidebar Next, Next, Next
4.Press sidebar Prev

Actual Results:  
Note that the URL 'start' parameter is wrong:

- There are two entries (should be 1)
- The numbers step up 0,10,20,30 then back down to 10.

Another bug:
Note also that there is 'memory' in the stepping in that if you search for
another term (like googler) and click Next, the start variable is still at the
old value (e.g. 30)

Expected Results:  
Step linearly.
Have single 'start' parameter.
Reset 'start' on new search.
Version: unspecified → Trunk
Confirmed on 1.8b2 on Windows XP. Searching "Google" brings you to the first 10
results. Pressing "Next" twice brings you to the next 10 results (20, 30), but
pressing "Prev" just once brings you back to the first 10 results.

Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8b2) Gecko/20050320
search
Assignee: sidebar → search
Component: Sidebar → Search
Product: Mozilla Application Suite → Core
Well, it turns out that this is a duplicate of bug 285539. It should be marked
as such.
(In reply to comment #3)
> Well, it turns out that this is a duplicate of bug 285539. It should be marked
> as such.

Ugh, make that bug 150337.
yup.  resolving as dupe

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