JDK-6379588 : WinLAF:Child popupmenu top border line is not coincident with parenet popupmenu top border line.
  • Type: Bug
  • Component: client-libs
  • Sub-Component: javax.swing
  • Affected Version: 6
  • Priority: P2
  • Status: Closed
  • Resolution: Duplicate
  • OS: windows_xp
  • CPU: x86
  • Submitted: 2006-02-01
  • Updated: 2011-02-16
  • Resolved: 2006-03-10
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
JDK 6
6Resolved
Related Reports
Duplicate :  
Description
BugInfo:
========
MouseOver on the JMenu option which is in popup menu as first item then it shows up child popup menu.But while comparing with native popup menu the following difference has been observed.

Child popup menu top border line is not coincidence with parent popup menu top border line while compare with native. But in native both parent and child top border lines are coincident.

Steps to Reproduce:
===================

1. Run the attached program in windows xp machine.

2. Open the magnifier which is available in Accessibility Menu in windows.

3. Click on "Click On Me" button.

4. Mouse over on the "Parent -1" Menu option.

5. See the gray color top border line of both parent and child popup menu in magnifier.

Expected Result:
================
Child popup menu top border line should coincident with parent popup menu top border line by compared with native.

Actual Result:
==============
The top border line of child popup menu is not coincident with parent popup menu top border line.

Please check the attached gif files for finding the difference.

Comments
EVALUATION Giving to Richard because he is working on the related 6379518
25-02-2006

EVALUATION The problem is reproducible for WinXP laf only
13-02-2006