On Fri, Dec 23, 2011 at 20:44, rupert THURNER <rupert.thurner@gmail.com> wrote:
On Fri, Dec 23, 2011 at 20:29, Brion Vibber <bvibber@wikimedia.org> wrote:
The floating, fixed-position header bar (header bar always at the same place at top of the screen while other things scroll) causes a number of problems in the app, including:

* https://bugzilla.wikimedia.org/show_bug.cgi?id=32917 - It's difficult to tap into the search box
* https://bugzilla.wikimedia.org/show_bug.cgi?id=31524 - section links on file pages scroll too far down

My 'absolute' branch resolves this by removing the 'position: fixed' floating toolbar and letting it scroll off the page:

This lets us drop the event handlers that screw up the search field focusing, because we don't need them to work around the bug where click events went through to the background elements. It fixes the scrolling / reference / hashlink issue by getting the header out of the way, so going to a position in the document actually shows it at the top of the screen.

It also provides more screen space for reading, which is a big plus in portrait orientation where a toolbar eats proportionately more screen space.

The downside is that if you've scrolled down on the page, you have to scroll back up to get to the search field etc.

This is pretty much how the stock web browsers on iOS and Android work, however, so I don't think it's such an awful thing to do. Any objections? Preferences on making things sometimes auto-pop up?

thanks so much for removing this space waste and provide more area for the article. android phones usually have a (hardware) search button, most of the time a magnifier symbol. this is used for searching the phone book as well for browsers, etc. is there any thing why you do not want to use it?
just as a reference for the ones not so familiar with android development: http://developer.android.com/guide/topics/search/search-dialog.html was the "android standard" way i was referring to.