User Agent String: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.1 ) Gecko/20020826 An example: if you open up the Search sidebar tab in basic mode and set the search engine to Google, a search for "foo" brings up results 1-10. If you look at the URL, the search sidebar has passed the parameter "start" twice, both with the value 0. If you then press Next in the search sidebar, you will get results 21-30. If you check the URL, the parameter "start" has been passed twice again, both times with the value 20. It looks like the code from google.src in the searchplugins/ directory is correct: <inputnext name="start" factor="20"> <inputprev name="start" factor="20"> Even though this code is correct, it seems to have a fundamental design flaw. The search engine needs to know not only the hit to start from, but also either the hit to end with or the length of hits to return. When, in the inputnext or inputprev tag, we simply say 'factor=20', we don't say HOW the necessary stopping point information will be passed. Will it be with an 'end' parameter, or a 'length' parameter or what? I suggest that the inputnext tag have a start name parameter, a length name parameter, and a factor size parameter.

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

This bug is more correctly a duplicate of a bug I reported a few months ago, bug 149931. I proposed a solution in that bug-report. I am unable to re-open and mark this bug as a duplicate, as I am not priviledged enough and do not own this bug. Doug, if you want to mark it as a duplicate of bug 149931 (and I think you'll agree it is if you read it) it'd be much appreciated! Sam

Yep, Sam is right here.

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