207179 - Next button inactive after 1st search from address bar

Status: RESOLVED DUPLICATE of bug 150333

(SeaMonkey :: Search, defect)

Description

[Cliff Dugal]

User-Agent:       Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.4b) Gecko/20030507
Build Identifier: Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.4b) Gecko/20030507

Normally, when you enter a string to search in the address bar and search for it
(using the search button or "Search Google for ..." drop-down function), the
search sidebar will show all the results, and you can navigate the results with
the Next, Previous buttons. But, any search done this way before the search
button was pressed in the sidebar panel will result in the Previous and Next
buttons remaining inactive.

Reproducible: Always

Steps to Reproduce:
1. Set Google as the default search engine (I haven't verified others).
2. Start a new browser window and show sidebar search panel.
3. Type in term, let's say Mozilla, into address bar, press up to select "Search
Google for "Mozilla"", then press Enter to start searching. The search results
are shown in the sidebar now, but the Next button is inactive.
4. Press the Search button in the sidebar search panel to search for Mozilla
again. Notice that the Next button is active now.
5. Search using the address bar again for any term. This time the Next button
will stay active and be useable.

Actual Results:  
After step 3. above, the Next button is inactive.

Expected Results:  
After step 3. above, the Next button should be active.

Instead of starting from a new window, the same results above can be obtained by
starting from a different sidebar tab (except that the search term is not
automatically shown in the Search panel). Actually, switching from the Search
tab to a different tab (e.g. Bookmarks), then back again will still show the
current search results, but clear the search term and disable the Next and
Previous buttons from any search.

Comment 1

[Erich 'Ricky' Iseli]

Next/Prev buttons cannot yet be used consistently. Dupe of bug 150333

*** This bug has been marked as a duplicate of 150333 ***