Announcement

Collapse
No announcement yet.
X
  • Filter
  • Time
Clear All
new posts

    Issue with Label and RadioGroupItem on iPad

    I'm facing a weird problem specifically on the iPad. My application contains an exam with a series of questions. The question is a StaticTextItem, and the answer choice set is a RadioGroupItem.

    After a few minutes (sometimes even seconds), the radio options (RadioGroupItem) just freeze and refuse the refresh going from one question to another. The question text changes, but the answer choices stay the same.

    Similarly the timer (which is a Label), also freezes. All the other elements on the page like StaticTextItem, Buttons, Checkboxes, Tabs etc., work just fine. Only the Label and RadioGroupItems freeze.

    In my code, I'm using setValueMap to set the values for RadioGroupItem and setContents to set the contents for Label. I also tried setting setRedrawOnChange(true) on both the elements, but it didn't make any difference.

    Once the problem starts, all the Labels in other parts of the application also freeze. The only way to get them to work again is to do a browser refresh.

    "I think" the problem started with iOS 6. It has been reproduced on iPad 2, and both 3rd and 4th Gen iPads. It happens both in Safari and Chrome. But I have not been able to reproduce it on the iPhone 4 running iOS 6. Also, it is "not" reproducible on PC / Mac, and any Android Device.

    It occurs only on the iPad.

    I know I should give a reproducible test case, but I haven't been able to reproduce it in a simple standalone test case yet.

    At this point, I'm just trying to find out whether anyone is aware of this issue. Also, can someone offer advise on how to go about troubleshooting the problem?

    Thanks in advance.

    P.S.: I have reproduced the issue with 3 different nightly builds of SmartGWT LGPL.

    a. 3.1d May 2, 2012
    b. 3.1d Nov 12, 2012
    c. 3.1p Dec 12, 2012 (latest as of today)
    Last edited by deepfriedbrain; 12 Dec 2012, 07:19.

    #2
    It sounds like a javascript problem within the browser. Have you checked the error console to see if there are any errors? Or the developer console?

    Comment


      #3
      Thanks for your response.

      I'm still trying to get familiar with iPad debugging. I enabled Web Inspector and debugging it from Safari on Mac.

      Under the Current Log, I can't see any Javascript errors even though the RadioItemGroup and Labels are frozen on the application. Should I be looking for those errors somewhere else?

      Is there an easier way to debug on the iPad? I'm familiar with Firebug. Sorry, but it's early days for me as far as the iPad is concerned. My app was developed on the PC and tested to work on PC / Mac. I didn't specifically test on iPad before, though I had not seen any major issues on iOS devices.

      Also, just to reiterate my point, the other elements (Question text, question no. etc. which have been implemented as StaticTextItem, buttons and tabs) are working fine. If there was a Javascript error, I suppose the other elements would not work either.
      I'll really appreciate any help.
      Last edited by deepfriedbrain; 12 Dec 2012, 09:14.

      Comment


        #4
        I also tried doing a redraw on the radio items and labels after changing their value, but it doesn't make any difference. Their values are still frozen.

        Comment


          #5
          1. I ran Firebug on Safari and Chrome on iPad, but there were no javascript errors in the console.

          2. Tried on 5 different browsers on iPad, and the problem was reproducible in every browser that I tried.

          3. Downgraded to SmartGWT SGPL 2.5p latest nightly, and had the same problem.

          4. Tried with GWT 2.3, 2.4, and 2.5, and had the same problem.

          I'm clueless now as to "why just iPad?".

          Does anyone know what's different with iPad compared to other devices (PC, Mac, iPhone, Android devices)?

          Comment


            #6
            Just connect the threads, deepfriedbrain has noticed a similar issue in the Showcase, that might have the same root cause.

            Comment

            Working...
            X