Announcement

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

    #31
    Hello Isomorphic,

    I thought you had ignored the issue as I was the only one who was facing the problem. But I'm delighted to see your response.

    Yesterday I spent about 6 hours investigating on this issue. Finally I've managed to create a standalone application to reproduce the issue and have deployed it on Google App Engine. The app URL is:

    http://testscrollbar.appspot.com

    Before you launch the application, resize your browser window to about 800 x 600px. You should be able to see the unnecessary horizontal scrollbar when the application is first launched. If you resize the window even slightly or refresh the window, the horizontal scrollbar will disappear. To get the horizontal scrollbar again, you'll need to launch a new browser window. Also, it's easier to reproduce the issue by using the incognito / stealth mode in Chrome.

    I've been able to reproduce the issue consistently on both Chrome (8x and 9x), and Firefox 3.6.x on 4 different machines (Window XP Home SP3, Windows XP Pro SP3 and Windows 7 Pro), in 2 different networks. I'm using the latest SmartGWT 2.5 LGPL binaries from 02/06/2011 nightly build.

    After the last round of fixes from your side, I could NOT replicate the problem on the standalone test case I posted in one of my previous posts above, but I could still see the problem in my real application intermittently. Therefore, I started stripping out code from my (real) application in order to isolate the problem. Finally, I could create a skeleton application with which I could reproduce the problem consistently.

    The only difference between the previous standalone application and the new application is an "RPC call" to a user Login Service, which I borrowed from a Google tutorial (http://code.google.com/webtoolkit/doc/latest/tutorial/appengine.html). This service authenticates the user using Google Account. Just before I call rootVLayout.show(), I call the login service to check whether the user is logged in. If I remove this RPC call, then the problem disappears.

    I'm not sure whether there's any real correlation between the RPC call and the issue, but that's the only thing which seems to make a difference.

    Do you think it would help if I email you the entire standalone Eclipse project? It does NOT have any of my application code. If so, please let me know the email address where I can mail the package. It is about 7.5 MB in size.

    Answers to your other questions:

    1. The problem occurs in both compiled mode and dev mode, but is intermittent. The problem is more frequent when the application is deployed to the app engine, than in the dev mode. In the dev mode, the problem only appears when I start the application for the "first time" after starting the hosted mode in Eclipse (using the 'Run' option). On subsequent tries, I cannot reproduce the problem even if I clear the browser cache and restart the browser. To reproduce the problem again, I need to shut down the hosted mode and start it again. I don't have to clear the browser cache though.

    2. I see the issue locally as well as when the application is deployed on GAE.

    3. I don't see any warnings on the server.

    4. Yes, I'm seeing this on multiple machines. I don't have any special settings on these machines. They do not share any common settings.

    5. I didn't do any testing with the developer console yet. Please let me know whether you prefer to get the standalone application and test it at your end, or you want me to run the tests and report the results. I'll be happy to do it either way.

    Thanks so much for your help.

    Comment


      #32
      If you want to send the standalone Eclipse project to support@isomorphic.com we'll take a look and let you know if we can find anything.

      Comment


        #33
        Hello Isomorphic,

        I've emailed the Eclipse project to the given email address.

        Thanks for your help.

        Comment


          #34
          My apologies for not updating this thread sooner.

          This issue was resolved by the Isomorphic team in the nightly build of 3/1/2011. I'm really thankful to them for their patience in working with me to get to the bottom of the issue and resolve it. Their support has far exceeded my expectations.

          Thanks again.

          Comment


            #35
            What was the issue in the end?

            Also, deepfriedbrain, you deserve special mention for your diligence in getting to the bottom of this. This thread is a good example of how much work goes into finding and fixing a problem.

            Comment


              #36
              Hi , Can any body update me of the latest news about this thread !!!!
              how can we resolve it Please !

              Comment


                #37
                As deepfriedbrain mentioned a couple of post ago this issue was resolved in the framework around 3/1/2011.
                If you believe you're encountering this same behavior, please post a simple standalone test case demonstrating the problem and we can take a look.

                Comment

                Working...
                X