I've found that if one was to rapidly fire the requestPreviousPage event on a requestPager, it will no stop you from going in to negative pages. I can't use the curentPage attribute as a guard (unless I'm doing something wrong), because the currentPage attribute waits until the request finishes to update.
Well I have fixed it by keeping track of the page manually, but it does feel kind of hackish, and it seems that it should be built in to the plugin
I agree that this should be built-in. Would anyone be interested in working on a patch to add this to the plugin?
Fix #90 extra query param should not be included in the query string …
…if the value is null