Bug 601744 - IE - vertical scrolling problem on Resource Config and Admin Plugins pages
Summary: IE - vertical scrolling problem on Resource Config and Admin Plugins pages
Alias: None
Product: RHQ Project
Classification: Other
Component: Core UI
Version: 1.4
Hardware: All
OS: Windows
Target Milestone: ---
: ---
Assignee: Ian Springer
QA Contact: Sunil Kondkar
Depends On:
Blocks: jon-sprint11-bugs
TreeView+ depends on / blocked
Reported: 2010-06-08 14:46 UTC by Jay Shaughnessy
Modified: 2013-08-06 00:37 UTC (History)
4 users (show)

Fixed In Version: 2.4
Doc Type: Bug Fix
Doc Text:
Clone Of:
IE7 (7.0.6000 on Vista), IE8 (8.06001.18702 on XP SP3)
Last Closed: 2010-08-12 16:47:30 UTC

Attachments (Terms of Use)
screenshot (error box not shown until you dbl click "error on page" (136.52 KB, image/png)
2010-06-08 14:48 UTC, Jay Shaughnessy
no flags Details
Screenshot-IE7 (89.29 KB, image/png)
2010-07-02 10:29 UTC, Sunil Kondkar
no flags Details
patch that fixes this issue (3.75 KB, patch)
2010-07-20 17:36 UTC, Ian Springer
no flags Details | Diff
patch to handle correctly the context menu as well as scrolling (6.39 KB, patch)
2010-07-21 15:11 UTC, Lukas Krejci
no flags Details | Diff
patch to get main.xhtml back to its original state prior to my change (1.12 KB, patch)
2010-07-21 22:28 UTC, Ian Springer
no flags Details | Diff

System ID Priority Status Summary Last Updated
Red Hat Bugzilla 609211 high CLOSED disable raw configuration support in GUI 2020-10-14 00:28:05 UTC

Description Jay Shaughnessy 2010-06-08 14:46:30 UTC
Using IE7 and the 2.4 beta CR1 I can't scroll down the resource configuration.  Instead the top part of the screen scrolls up. See attachment.

This makes it impossible to properly view or edit resource config that extends past the bottom of the page.  For example, visit RHQ Agent resource config.

Comment 1 Jay Shaughnessy 2010-06-08 14:48:35 UTC
Created attachment 422229 [details]
screenshot (error box not shown until you dbl click "error on page"

Comment 2 Jay Shaughnessy 2010-06-08 14:59:59 UTC
I have not been able to get this behavior in the connection properties config page, it may be local to the resource config page.

Comment 3 Ian Springer 2010-06-08 15:27:05 UTC
I see the scrolling issue on the resource configuration on IE8 as well.

Comment 4 Charles Crouch 2010-06-08 20:50:01 UTC
Further breakdown of the issue:
c) Resource configuration not scrolling correctly. 
    Seen in IE8(ian), IE7(jay,charles), but not in IE8(joe,charles) or IE6(joe). Note the conflict, above.
d) Plugin configuation not scolling correctly. 
    *NOT* seen in IE7 (charles), IE8(charles)

IE Browser Versions:
charles: 7.0.7530.13
Jay: 7.0.6000.16890
joseph: 6.0.2900.5512.xpsp_sp3_gdr.100216-1514 
joseph: 8.0.6001.18702
charles: 8.0.7600.16385
ips: 8.0.6001.18702

This is only readily reproducible on IE7, so setting to High rather than Urgent

Comment 5 Ian Springer 2010-06-29 00:22:37 UTC
The scrolling issue appears to be caused by the rich:tabPanel tag that is used for the tabs used to switch between structured and raw config views. The following bug describes how rich:tabPanel can cause issues on IE7:


I added the following to win.css:

.rich-tabpanel-content-position {
   position: static;

This fixed the vertical scrolling so that it included the resource config. However, the "Basic Mode" tab itself does not scroll with the rest of the page, but instead remains in its original position, as if it either is positioned absolutely or has a different z-index. I tried some of the IE hacks described in this article but after a couple hours of hacking was not able to get everything working as it does on FF.

Comment 6 Charles Crouch 2010-06-29 01:13:14 UTC
If turning off raw config in the GUI fixes this issue, then thats acceptable for JON2.4 where we don't have any plugins that utilize it. 

If the concensus is that raw config is required for RHQ3 then we should apply this change after we've cut the RHQ3 build

Comment 7 Ian Springer 2010-06-29 18:13:40 UTC
This issue also exists on the Administration > System Configuration > Plugins page, which also uses the RichFaces tabPanel component.

It turns out the fix for the issue is the one Nick B describes in his comment on https://jira.jboss.org/browse/RF-6030:

Add "position: relative" CSS to elements that have scrolls as a workaround.

This fix has been implemented for both affected pages by commit b2bd54e, which has been pushed to the release-3.0.0 branch:

1) /rhq/layout/main.xhtml modified to fix Resource Configuration > Current page.
2) /rhq/entity/layout/main.xhtml modified to fix Administration > System Configuration > Plugins page.

Test Steps
1) Verify that vertical scrolling works correctly for both the Resource Configuration > Current page and the Administration > System Configuration > Plugins page. Make sure the vertical size of the content is bigger than the viewport, so vertical scrolling kicks in.
2) Test on IE6, IE7, IE8, FF2, and FF3.

Comment 8 Ian Springer 2010-06-29 21:19:55 UTC
Commit e6438c4, pushed to release-3.0.0, fixes an issue caused by the original fix, which was causing the vertical scrollbar on Resource tab pages to be displayed by FF at 2/3 of the correct width.

Comment 9 Charles Crouch 2010-06-30 17:27:21 UTC
Reducing priority to clarify QA testing order

Comment 10 Sunil Kondkar 2010-07-02 10:19:59 UTC
Verified on JON 2.4 GA_QA build#49 build.

Vertical scrolling works correctly for both the Resource
Configuration > Current page and the Administration > System Configuration >
Plugins page on below browser versions:

IE versions:

Firefox Versions:

The vertical scrollbar is displayed and works correctly on Administration > System Configuration > Plugins page on IE version 7.0.5370.11. 

However observed that the vertical scrollbar is not displayed on Resource Configuration > Current page  on IE version 7.0.5370.11. 

Please refer the attached screenshot.

Comment 11 Sunil Kondkar 2010-07-02 10:29:12 UTC
Created attachment 428942 [details]

Comment 12 Ian Springer 2010-07-20 17:35:29 UTC
This has been fixed (and tested in IE7 and FF3) via commit 070e961. However, it has NOT been pushed to origin, since it still needs to be tested on IE6, IE8, and FF2. The attached patch can be used by other devs to test the fix on those browsers.

Comment 13 Ian Springer 2010-07-20 17:36:51 UTC
Created attachment 433225 [details]
patch that fixes this issue

Comment 14 Lukas Krejci 2010-07-21 13:02:11 UTC
This patch seems to correct the issue in IEx (I didn't try FF2 yet) but causes another issue - the content pane covers the context menu in leftnav instead of the context menu appearing on top.

Comment 15 Lukas Krejci 2010-07-21 15:11:55 UTC
Created attachment 433444 [details]
patch to handle correctly the context menu as well as scrolling

Adding another patch that should preserve the correct viewing of the context menu along with the scrolling for IEx.

Comment 16 Ian Springer 2010-07-21 17:19:42 UTC
I tried out Lukas's patch, and the vertical scrolling works correctly on IE7 and FF3 on Windows. However, there is one minor issue on IE7 - the width of the right content pane is always about 10-20 pixels wider than the right hand side of the browser, so a horizontal scrollbar is always displayed and the user must scroll to the right to see the rightmost 10-20 pixels of the content. Lukas, I'm curious - do you see the same thing on IE6 and/or IE8?

In any case, I still think it's worthwhile to apply this patch, even in its current state. Otherwise, IE7 users will have no way to see the lower portion of the right pane's content on any resource/group pages where the content is too tall to all fit at once in the browser window.

Comment 17 Ian Springer 2010-07-21 17:22:46 UTC
Note, Lukas said he'd already successfully tested his patch against IE6, IE8, FF2, and FF3.6.

Comment 18 Ian Springer 2010-07-21 22:25:56 UTC
I'm attaching a patch that reverts /rhq/entity/layout/main.xhtml back to where it was before I made any changes for this issue. The vertical scrolling on the Resource Config>Current page should still work in IE7, since the rich:tabPanel that I believe was causing the issue is gone now that raw config support has been removed from the GUI. Lukas, first thing your tomorrow morning, would you please try stashing your changes, applying this patch, and then trying out the Resource Config>Current page in IE6, IE7, IE8, FF2, and FF3? As soon as I come online tomorrow, around 8:00-8:30am EST, I'll ping you to see how it's going.

Comment 19 Ian Springer 2010-07-21 22:28:52 UTC
Created attachment 433531 [details]
patch to get main.xhtml back to its original state prior to my change

Comment 20 Lukas Krejci 2010-07-22 12:07:00 UTC
I can confirm that main.xhtml in the original state behaves correctly wrt this bug in all browsers tested (IE6, IE7, IE8, FF2, FF3.6.4), although I think you have the patch reversed, Ian.

I created a separate bug 617179 for the context menu rendering problems and attached an isolated patch for that issue to that bz.

Comment 21 Lukas Krejci 2010-07-22 14:57:34 UTC
In addition I can confirm that the plugin list page in Administration > System Configuration > Plugins works in all the above mentioned browsers.

Comment 22 Charles Crouch 2010-07-22 15:22:27 UTC
This actually should reduce the amount of change (historically at least) by backing out some unnecessary fixes. It also makes resource config usable in IE7 which was the original bug

Comment 23 Lukas Krejci 2010-07-22 17:00:33 UTC
commit 8d6b4f8b43d62b7375468b363af0c1841c7d3a05
Author: Lukas Krejci <lkrejci@redhat.com>
Date:   Thu Jul 22 18:52:14 2010 +0200

    BZ 601744 - backing out the position:relative part of the original fix in main.xhtml. This effectively reverts the page to the state it was before we had the rich:tabPanel, which was eventually removed.

Comment 24 Corey Welton 2010-07-23 04:47:08 UTC
Going to go ahead and mark this verified.  Tested the behaviour against different browsers (IE, FF) and things [still] work [again]. -- the back-out appears to have been successful.

Comment 25 Corey Welton 2010-08-12 16:47:30 UTC
Mass-closure of verified bugs against JON.

Note You need to log in before you can comment on or make changes to this bug.