Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>Well, it's 1.0 Alpha 1, so I'd say the risks are:</p> <ol> <li>It's largely untested, so you'll probably come across unknown or unresolved bugs as you forge new ground.</li> <li>There is great potential for change in an early release, so you may have to update large swaths of your site, ie. when they namespace the data elements under "ui."</li> </ol> <p>It's also important to consider the reasoning behind those grades:</p> <blockquote> <p>What do the grades mean? The grades are a combination of the browser quality combined with the browser’s relevance in the larger mobile market.</p> </blockquote> <p>An "A" grade is an indication of the browser's capabilities, not any current or future compatibility with jQuery Mobile.</p> <p>If you want to help develop a new piece of software, start using jQuery Mobile, and contribute feedback, bug reports, code, or all of the above. If not, the team is hoping to see a 1.0 release in January 2011, which is just around the corner.</p> <p>The theory around jQuery Mobile is providing a rich experience to rich browsers, and a functional experience to the more basic browsers. I think this is reasonable, especially considering how fast jQuery Mobile can get you up and running with a really great mobile UI.</p> <p>I'd like to know what you mean by "a site that isn't primarily for mobile user." There are sites that are optimized for mobile, and there are sites that <em>aren't yet</em> optimized for mobile. Only some very specific niche sites don't require a mobile experience.</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload