-
Notifications
You must be signed in to change notification settings - Fork 2.4k
Current development status
Updated March 25, 2011 // This is the current status of our supported platforms and browsers, listed in alphabetical order.
All features work and pages render 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.
All features work and pages render 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.
-
The slider handle isn't draggable, so you either need to enter a value into the text input or click the handle to focus it, then tap the slider track to jump it to a new position. We're looking into ways to make this work better on this browser.
We are still actively debugging this browser to see how good an experience we can provide (can we provide an A grade experience?). There are a fair number 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 all navigation within the jQuery Mobile Ajax experience isn't tracked as steps in the history and the Back button doesn't work as expected. We've had RIM engineers look into this issue and there doesn't seem to be any way to get a hashchange event to be added to the history stack, so this isn't a fixable bug. 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.
All features work and pages render as designed in the latest builds of Firefox Mobile on Android. Known issues and workarounds:
- The slider handle isn't draggable, so you either need to enter a value into the text input or click the handle to focus it, then tap the slider track to jump it to a new position. We're looking into ways to make this work better on this browser.
All features work and pages render 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 really well. The iOS platform probably has the best overall experience because of the hardware-accelerated transitions and full support of CSS3 properties for shadows, gradients, and rounded corners. We have included a full set of retina display optimized icons that are automatically applied to any device with a very high resolution display.
We don't currently have any test devices for this platform, so support is unknown. We need to get better device and emulator coverage to assess the feasibility of supporting this for the 1.0 release.
All features work and pages render as designed in Opera Mobile 10.1 and Opera Mini on Android. Known issues and workarounds:
-
The slider handle isn't draggable, so you either need to enter a value into the text input or click the handle to focus it, then tap the slider track to jump it to a new position. We're looking into ways to make this work better on this browser.
-
On Opera mini, the custom select menus are positioned at the top of the screen, so they look broken. We're looking into a fix for this.
-
On pera mini, pages don't scroll to the top during transitions which can lead to issues when linking back from the bottom of a long page because you end up viewing what appears to be a blank page. This is a critical issue we're working on solving.
All features work and pages render 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 an overlay or toolbar on the screen. For this reason, we make sure that the fixed-position toolbars will not be 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
multipleattribute so choosing to use a native select menu for multi-select controls will result in an unusable form on this platform. We recommend using the custom control we provide in mobile for these situations. -
The slider handle isn't draggable, so you either need to enter a value into the text input or click the handle to focus it, then tap the slider track to jump it to a new position. We're looking into ways to make this work better on this browser.
-
CSS gradients aren't supported by this browser, so the flat background color is rendered instead. Text- and box-shadow don't seem to be supported as well, but these gracefully degrade.
-
CSS transforms/animations aren't supported, so pages just switch without transitions
We don't currently have any test devices for this platform, so support is unknown. We need to get better device and emulator coverage to assess the feasibility of supporting this for the 1.0 release.
We are still actively debugging this browser to see how good an experience we can provide. In alpha 3, we managed to track down a pretty major script bug that was completely preventing the page from being enhanced at all. At this stage the pages render pretty well, but there are some rough spots that need debugging. Known issues and workarounds:
- Like BB5, there is no support for hash change tracking in this browser, so all navigation within the jQuery Mobile Ajax experience isn't tracked as steps in the history and the Back button doesn't work as expected. 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. 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.
As of Alpha 4, we now support WP7 and have been testing on a HTC Surround phone. All core features are fully functional and we're just working on tweaking performance and closing bugs. The browser in the current version of WP has similar capabilities as IE7 on the desktop so there is no support for advanced CSS properties like border-radius, bo- and text- shadow that we use extensively in the framework so some of the visual polish isn't present. In late 2011, Microsoft plans to replace the rendering engine with IE9 which will dramatically improve the speed and rendering quality.
If our coding practices are followed (PE, semantic markup), sites built with jQuery Mobile should be functional on any device that understands HTML, including basic featurephones. We still need to develop an attractive basic stylesheet that can provide better baseline styles for these devices.
The Amazon Kindle supports jquerymobile for most features.