I launched the application when the window was NOT maximized, but wide enough to accommodate the contents, I still got the horizontal scrollbar. But as soon as I resize (increase or decrease) the window, the horizontal scrollbar disappears.
Hello Isomorphic,
Were you able to replicate this issue on Chrome? Do you need any other information from my side?
The (unnecessary) horizontal scrollbar appears only on the initial load of the application. Once the window is resized, the horizontal scrollbar disappears.
Thanks for your help.
Hi DFB,
We have found this issue is intermittent.
For us the following steps seem required to reproduce it:
- clearing browser cache
- load the page
- reload the page
Given these steps we’ve managed to come up with a fix which has been introduced to our mainline codebase and will be present in the next nightly build.
The fact that you’re reproducing this so readily when for us it is very much intermittent may possibly indicate something else is going on here so please try the next nightly build (It’ll be available Dec 22 am) and let us know if you do continue to see this issue.
Thanks
Isomorphic Software
Hello Isomorphic,
I tested with the 12/23 nightly build and it’s rocking now. Tested on Chrome, FF and IE, and everything looks good now.
I really appreciate your help and prompt action in resolving this issue.
Thanks a lot.
Hello again Isomorphic,
Unfortunately, the issue has moved from Chrome to Firefox now. I’m seeing the unnecessary horizontal scrollbar in Firefox when the app first loads. The scrollbar disappears as soon as the window is resized in any manner. Chrome seems to be working fine now.
The problem is intermittent this time. I don’t see it every time, but it’s there more often than not.
My FF version is 3.6.13, and I’m on 12/23 nightly build.
Thanks.
We were unable to reproduce this behavior in house but have applied a workaround that should ensure it doesn’t happen in any browser.
The next nightly build will include this change - we’d recommend you try your test case with that build. We’re confident that the problem should no longer be reproducible!
Hello Isomorphic,
I downloaded the latest nightly (1/6) and am testing the application now. So far it looks good. I do see the (unnecessary) horizontal scrollbar while the application is loading, but it disappears as soon as the app is loaded completely. It’s the same in Chrome and FF.
Let me test it thoroughly for another week or so. I’ll come back and post the updates.
Thanks a lot for following up so closely on this issue.
Have a great 2011!
Hello Isomorphic,
One week has gone by and I’m back with the updates. Unfortunately, the news isn’t good. I still see the horizontal scrollbar intermittently. It happens on both Firefox and Chrome (the same versions that I mentioned before). I cannot find a pattern to reproduce the problem consistently though. Sometimes, on the initial load the scrollbar momentarily appears and then disappears when the page finished loading. But it comes back when the page is refreshed (using Browser refresh). Also, any resize of the window immediately removes the horizontal scrollbar.
I tested it on 3 different machines - Mac OS X 10.6.6, Windows XP Home SP3, Windows XP Pro SP3. I’m using SmartGWT LGPL 2.4 1/6/2011 nightly. I verified the correct date stamp on ISC_Core.js using Developer Tools in Chrome (the approach you suggested earlier).
Please let me know if you need any additional info from me or want me to test something.
Thanks for your help.
Hi Guys,
We’re not able to reproduce this in house at all. We also haven’t been hearing any other reports of this issue.
This makes it seem like there must be something special about your setup which is causing the behavior.
Firstly on the project side: In previous posts you’ve taken us through your setup and it sounds pretty standard. We may be rehashing old ground here but can you do a sanity check test of
- creating a new project
- adding the SmartGWT jars to it
- modifying the .gwt.xml file to include SmartGWT
- modifying the bootstrap file to remove the default HTML
- modifying the entry point class to display your code
And verify that you’re still seeing the problem.
If so, could you post the .gwt.xml file, the bootstrap file and the entry point class file so we can exactly duplicate your project on our end and retest.
Be sure to lay out exactly the steps to reproduce the problem!
Also - in this case does the problem occur in both compiled mode and dev mode, or just in dev mode?
Does it make a difference if you’re hitting the app locally (So the browser is running on the same machine as Eclipse / Jetty) vs across a network?
Do you see any warnings on the server?
Secondly, on the browser side: You’re seeing this on multiple machines / browsers. Are there any settings shared by these setups we should be aware of? For example locale settings? Screen resolution?
Beyond that, some debugging you could try with the developer console:
- When in the bad state, what is the reported width and height of the page (evaluate “isc.Page.getWidth()” and “isc.Page.getHeight()”)
- If you go to the Watch tab you should see a tree of the visible set of components. Right click on the header and show the “specified size” and “drawn size” columns. What is the specified / drawn size of the outermost layout?
- If you evaluate “isc.Browser.isStrict” what do you see?
- Once you’re in the bad state - if you evaluate “isc.EH.$hr()” does the problem fix itself?
Thanks
Isomorphic Software
This issue of unwanted/needed scroll bars was driving me batty before too. I found two things that fixed it:
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:
-
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.
-
I see the issue locally as well as when the application is deployed on GAE.
-
I don’t see any warnings on the server.
-
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.
-
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.
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.
Hello Isomorphic,
I’ve emailed the Eclipse project to the given email address.
Thanks for your help.
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.
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.
Hi , Can any body update me of the latest news about this thread !!!
how can we resolve it Please !
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.