Personally I would prefer a stop button that works immediately to freeze the state of the browser - no more loading, no more scripting (absent further input) and what is now visible remains so _rather than the screen clearing_ as it often does.
Essentially, I often accidentally trigger touches on links I didn't mran to load, but almost never hit the address bar stop button by mistake. I'd probably be content with just the popup menu stop button though. On Sep 11, 10:16 pm, nyliferocks <[email protected]> wrote: > I often find myself hitting inside the address text area to stop a > page from loading. Either someone hours the browser back/forward > button by accident our a quickly typed url is normally two to reasons > we would want a page to stop loading immediately. We often have a > completed form when this happens and end up losing what we typed in. > > Several times I find that the stop button doesn't work in time but my > main point here is to eliminate an unnecessary button to clear up some > browser interface where just hitting the url address bar would be just > as useful, if not more. > > The longer size and a reduced action response time may play into this > saving us another split second of our time or a website form complete > filled out. -- You received this message because you are subscribed to the Google Groups "Android Discuss" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/android-discuss?hl=en.
