Unguard the q method

@wedaly @cpennington 

Is there a reason that the q method should not be unguarded?

As is currently, putting a query in the is_browser_on_page method sends you into an infinite loop, as shown via `./run_tests.sh test_next_page.py` with the modified next_page definition from this PR.

Also not sure if you'd prefer a separate test case to piggybacking onto the next page tests.