I hate using my Android phone (especially its web browser) for this very reason. It frustrates me to no end. Sometimes, even when I think that the content is lo

I hate using my Android phone (especially its web browser) for this very reason. It frustrates me to no end. Sometimes, even when I think that the content is loaded (because the image is static for a few seconds), it's actually not - and tapping on the screen creates a UI event that is parsed a couple seconds later, after the screen scrolls because of a previous scroll that I thought was ignored. I believe it's built this way because of modularity - the input drivers know nothing about the content of the screen, and once the event is finally registered, it cannot "go back in time" to figure out where the click is supposed to go - it can only send the event and let the user application handle it. The solution, it seems, would require some serious integration of the system with the UI toolkit.