Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>My team at work is also using jQuery Mobile and encountered similar problems on devices (though I don't think we've seen a simulator crash from this). Here's what we've found so far:</p> <ul> <li><p>Your call to <code>show()</code> may be working, but be processed so slowly that you give up before it loads. <a href="http://208.74.204.192/t5/Web-and-WebWorks-Development/application-slow-on-device-fast-on-simulator/m-p/1134563/message-uid/1134563/highlight/true#U1134563" rel="nofollow">The entire DOM for the web page is processed every time you add, remove, or modify any attribute or element on the page</a>. A BlackBerry Forums post suggests <a href="http://supportforums.blackberry.com/t5/Web-and-WebWorks-Development/PLEASE-READ-PERFORMANCE-TIP-Speeding-up-your-UI/td-p/498596" rel="nofollow">removing an element before modifying</a> it to increase performance.</p></li> <li><p>On some devices we've found that a call to <code>show()</code> will work, but the UI is only updated after scrolling up or down on the page a bit. If your page is too short to scroll, you might be out of luck.</p></li> <li><p>The <code>onclick</code> attribute appears to be ignored on touch screens (but works fine on trackball/touchpad devices), and may be why your <code>show()</code> call results in no action. To make our hyperlinks work on all devices, we place JavaScript calls in both the <code>onclick</code> and <code>href</code> attributes:<br> <code>&lt;a href="javascript:showThings();" onclick="javascript:showThings();"&gt;Show&lt;/a&gt;</code></p></li> <li><p>When invoking JavaScript from an <code>onclick</code> method, we've had to prepend the method call with <code>javascript:</code> like so:<br> <code>&lt;a href="#" onclick="javascript:showThings();"&gt;Show&lt;/a&gt;</code><br> (Most modern browsers assume that your <code>onclick</code> value should be evaluated as JavaScript)</p></li> <li><p>Focus-based navigation is not enabled by default, which caused us problems when using trackball/thumbpad devices (the screen would lock up and stop responding to key presses). You can enable focus-based navigation <a href="http://docs.blackberry.com/en/developers/deliverables/27265/Using_focus_based_navigation_1589503_11.jsp" rel="nofollow">in either your project's <code>config.xml</code></a> or by using a <a href="http://docs.blackberry.com/en/developers/deliverables/30595/Defining_initial_focus_1589507_11.jsp" rel="nofollow">RIM-specific hyperlink attribute</a>. I forget what issue we encountered after enabling this in <code>config.xml</code>, but we ended up going with the <code>x-blackberry-initialFocus</code> hyperlink attribute instead.</p></li> </ul> <p>It's hard to say exactly which of the above points might apply to your situation, hopefully something is relevant or useful. My team has been unimpressed so far with the web development experience on BlackBerry, particularly the differences seen between OS 5 and 6, and between trackball/thumbpad and touch devices.</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. This table or related slice is empty.
 

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