After extensively testing both of the primary scrolling options for jQuery Mobile I feel like the jQuery Mobile Scrollview is the best solution. It was very easy to install and configure, offered great support on iPhone and Android devices, and has more options and configurations available to customize your application. In addition, it may at some point be integrated into jQuery mobile as default functionality to serve as a bridge until position:fixed and overflow are full supported by the majority of active smartphones.

The process of loading a URL in a new tab on iPad can be rather cumbersome and slow. First, one launches Safari from the home screen, waits for the app to open and the old webpage to re-render, then one hits the tab switch button, presses the new tab space, waits for that tab to open, waits for it to switch to the search panel (this is the most irritating part of the process, since it seems to take even longer when what one really wants is the URL bar), and finally, one clicks on the URL bar to enter in a new URL.

To simplify this process considerably, just add a new icon to your Springboard that goes directly to about:blank. Details after the jump.

Even from the earliest brainstorming days for our new version of Gmail for iPhone and Android-powered devices, we knew we wanted to try something novel with menu actions: a context-sensitive, always-accessible UI element that follows conveniently as a user scrolls. Thus, the "floaty bar" was born! It took us a surprisingly long time, experimenting with different techniques and interactions, to converge on the design you see today. Let's look under the covers to see how the animation is achieved. You may be surprised to find that the logic is actually quite simple!

iOS 4.2 is a free update for every iPhone, iPod or iPad device available now. This new release provides some major changes on HTML5 and W3C future standards support, like WebSockets and Accelerometer support, print support, new JavaScript data-types and better SVG support.

Apple didn’t update yet Safari documentation to reflect these new APIs. This information is based on JavaScript research and testing over Safari itself I’ve been doing.