Bug 820590 - Error in CSS style in jUDDI web console menu
Summary: Error in CSS style in jUDDI web console menu
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: JBoss Enterprise SOA Platform 5
Classification: JBoss
Component: jUDDI - within SOA, Build Process
Version: 5.3.0 GA
Hardware: Unspecified
OS: Unspecified
high
low
Target Milestone: ER4
: 5.3.0 GA
Assignee: Nobody
QA Contact: Matej Melko
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-05-10 12:32 UTC by Robert Balent
Modified: 2025-02-10 03:19 UTC (History)
4 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2025-02-10 03:19:49 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)

Description Robert Balent 2012-05-10 12:32:36 UTC 
In jUDDI web console, when you hover over the upper right menu, you will see the font-weight has changed and the menu flickers.

How to reproduce:
1. Open http://localhost:8080/uddi-console/uddibrowser.jsp
2. Log In
3. Hover your mouse over some item in upper right menu


How to repair:
You can see in CSS file (css/soa.css), there is:

#HeaderRight table td a:hover {
	color: #0000cc;
	background-color: white;
}

it should be:

#HeaderRight table td a:hover {
	background-color: white;
	color: #0000CC;
	font-weight: bold;
}
Comment 1 Julian Coleman 2012-05-31 09:52:26 UTC 
Resolved with revision 11141 of:

  src/main/resources/eap/ROOT.war/css/soa.css

Commit message:

  BZ 820590
  
  Add "font-weight: bold;" to "#HeaderRight table td a:hover", as "a:hover" in
  soa.css is overridden by the definition in uddiportlets.css, causing the
  bold attribute to be lost in the UDDI console.
Comment 4 Suz 2012-06-13 05:59:19 UTC 
I have set the technical note field to negative as this appears to have been detected and fixed in the same version, so users will not have seen it.
Comment 5 Robert Balent 2012-06-21 12:29:00 UTC 
Verified with SOA-P 5.3 ER4
Comment 10 Red Hat Bugzilla 2025-02-10 03:19:49 UTC 
This product has been discontinued or is no longer tracked in Red Hat Bugzilla.
Note You need to log in before you can comment on or make changes to this bug.