Current development status

Supported platforms // Updated January 22, 2010

iOS 3.x-4.x

All features work as designed across all iOS test devices, including iPhone, iPod touch, iPad and emulators. We would like to improve overall responsiveness and smooth out page transitions but everything is working.

Android 1.6-2.3

All features work as designed across our Android test devices: HTC Incredible (2.2), Motorola Droid (2.2), Nook Color (2.1), and Google G1 (1.6) or any of the emulators. Navigation with the touchscreen works great, but the navigation roller ball has some issues on some text inputs, the flip switch, slider and selects that can be solved. Older devices like the G1 can be laggy and become unresponsive on more complex pages.

Palm/HP WebOS

All features work as designed on the Palm Pixi or Pre test devices running 1.4 or the emulators. Known issues and workarounds:

• The current scroll offset (scrollTop property) isn't reported correctly by this browser so it's not possible to accurately position an element like a overlay or toolbar on the screen. For this reason, we make sure that the fixed position toolbars will not by dynamically positioned on this platform on scroll and instead are positioned inline. On the custom select menus, we don't show the smaller, floating select menu for short lists and always use the full-page style menu to avoid positioning issues.
• The native browser doesn't properly support select elements with the multiple attribute so choosing to use a native select menu for multi-select controls will result in a unusable form on this platform. We recommend using the custom control we provide in mobile for these situation.

Blackberry 6

All features work as designed on the test devices, including the Torch and Style devices, as well as the emulators. We have been testing features with both touch input and the cursor-based input via the touchpad. Known issues and workarounds:

• The webkit-based browser has a serious display bug that causes the background color of an element to bleed outside of a rounded corner if both border-radius and box-shadow CSS properties are applied on the same element. This was causing all the lists, buttons and form elements to look very rough so we have implemented a workaround to not apply the box-shadow to elements on this browser to improve the rounded corners rendering.

Blackberry 5

We are still actively debugging this browser to see how good an experience we can provide. There are a fair amount of rendering and script issues and some clicks are being lost so this platform is pretty rough. Known issues and workarounds:

• There is no support for hash change tracking in this browser so when using the Ajax-based navigation system, the Back button does not move you back through the history stack, instead you go the last web page before the first mobile page. We've had RIM look into this issue and there doesn't seem to be any way to get a hashchange to be added to the history stack so this isn't a fixable bug so we're actively looking into ways to detect hashchange support to downgrade failing browsers into a non-Ajax navigation system (i.e. each link will load a new page) which is probably our best option.

View All Pages