GoodSearch results page loads with keyboard open...

GoodSearch.com's search engine (which works normally with Chrome and Opera Mobile on the same device) does not work smoothly with Firefox for Android. When the results page loads, the keyboard is opened too, obscuring much of the page (the trouble seems to stem from the cursor loading within the search input box -- perhaps the default behavior of the page).

I also have difficulty getting scrolling the page even after dismissing the keyboard. As though having the caret in the text input box prevents my "swiping" from registering properly.

GoodSearch.com's search engine (which works normally with Chrome and Opera Mobile on the same device) does not work smoothly with Firefox for Android. When the results page loads, the keyboard is opened too, obscuring much of the page (the trouble seems to stem from the cursor loading within the search input box -- perhaps the default behavior of the page).
I also have difficulty getting scrolling the page even after dismissing the keyboard. As though having the caret in the text input box prevents my "swiping" from registering properly.

Question owner

Ah, that certainly makes this "not a support question" then. Which is fair.

Unfortunately an inconvenience like this, which is not experienced in other mobile browsers (Chrome / Opera) is a problem - in a competitive sense.

I'm all for standards compliance and standardized behavior, but Chrome/Opera might be "right" to ignore that request... when would this ever be desirable behavior on mobile?

I'll take this up with GoodSearch themselves, but I suspect "Hey, your site design is inconvenient for just one browser which has less than 1% of the mobile market share" won't be a very compelling call to action. I was a web designer, years ago, and I know my reaction to that would have been the polite version of "then don't use that crappy browser"

Thanks for shedding some light!

Ah, that certainly makes this "not a support question" then. Which is fair.
Unfortunately an inconvenience like this, which is not experienced in other mobile browsers (Chrome / Opera) is a problem - in a competitive sense.
I'm all for standards compliance and standardized behavior, but Chrome/Opera might be "right" to ignore that request... when would this ever be desirable behavior on mobile?
I'll take this up with GoodSearch themselves, but I suspect "Hey, your site design is inconvenient for just one browser which has less than 1% of the mobile market share" won't be a very compelling call to action. I was a web designer, years ago, and I know my reaction to that would have been the polite version of "then don't use that crappy browser"
Thanks for shedding some light!