Strange behavior on the issues.aspx page
The following behavior is bit odd.
I initially tested v3.0.4 on my machine and it's fine. The Issue.aspx renders fine.
I installed v3.0.4 on our production server, and it seems most of the page render fine, but the issue.aspx has an odd behavior. After this page loads, it displays the bottom portion of the issue page.
I tried resizing the page of various size, but it always displays a page where it scrolls down to the view buttom.
I tried this on our developers machines and i got the same behavior. -on IE7
I tried on the server, same behavior. - on IE7
but on Firefox, it displays correctly. It displays top of the issue.apsx, and doesn't scroll down.
Any ideas?
KilShon
· 1 |
|
Saturday, September 6, 2008, 1:59:55 AM |
0
|
Is it possible to send a screen capture to support at countersoft dot com? Also, can you test your browser on our site: http://gemini.countersoft.com?
|
||||
|
0
|
SaarCohen, I sent the screen shot to support@countersoft.com I also tested my browser on your site: http://gemini.countersoft.com It seems like the page is refocusing on the 2nd "View" button. Is there a javascript library that I may have not loaded or referenced? Per my original post, I'm not having this problem on my test machine, but when I deployed it to production box, this problem occured. On the test machine, I tried the automated deployment, but initially didn't work, so I deployed manually. On the production box, I deployed manually. Could this a problem? |
||||
|
0
|
Just to confirm, the only issue is with this specific production server, correct? If so try running: aspnet_regiis -i on the server. |
||||
|
0
|
aspnet_regiis - i didn't work. I tried on other production server, and tried both manual and automatic install. Same behavior. The issue page scrolls down to the 2nd view button. Weird thing is that I also tried installing it on a test box, and it's fine. The test box are similarily configured as the production box.
|
||||
|
0
|
Can you please try to comment out the last view button in the prodcution issues.aspx page?
|
||||
|
0
|
You beat me to it. Our developers and I were talking this over, and this morning we commented out the 2nd view button. It now works as I expected, no scrolling down to the page to the 2nd view button. I noticed that the first button is tagged as "btnG02", and the 2nd view button as "btnGo". So our guess is that in the code behind you have focus on btnGo, or focus is being defaulted to btnGo. I presume both top and bottom view button provides the same function, so if I update the issue.aspx page to use btnGO2 for both top and bottom button, will this cause any problem?
|
||||
|
0
|
Swap the 2 (btnGo -> btnGO2) and should be fine. We will fix this for the next release. |
||||
|