United StatesChange Country, Oracle Worldwide Web Sites Communities I am a... I want to...
Bug ID: 6519005 regression: Selection the item on the choice don't work properly in vista ultimate.
6519005 : regression: Selection the item on the choice don't work properly in vista ultimate.

Details
Type:
Bug
Submit Date:
2007-01-30
Status:
Closed
Updated Date:
2011-05-17
Project Name:
JDK
Resolved Date:
2011-05-17
Component:
client-libs
OS:
windows_vista,windows_xp
Sub-Component:
java.awt
CPU:
x86
Priority:
P3
Resolution:
Fixed
Affected Versions:
6u10,7
Fixed Versions:
7

Related Reports
Backport:
JDK-2167826 - regression: Selection the item on the choice don't work properly in vista ultimate.
Duplicate:
JDK-6553302 - Non-focusable AWT Choice doesn't allow user to change selection
Duplicate:
JDK-6565719 - REG: Items are not selectable using mouse, from Choice added to a Window - Win32
Duplicate:
JDK-6711954 - PIT:REG: Choice takes a couple of clicks to select an item, Vista
Relates:
JDK-4338368 - In Windows, Mouse Events are triggered by choice when it loses focus

Sub Tasks

Description
Selecting the item in the choice does not work properly when the focus is brought to & from the choice.  
Step to reproduce:
-------------------
1) Run the attached code.
2) Press "Tab" to move the focus on the Choice & move the focus back on the button  & once again on the choice.
3) Click on the choice & try selecting any item, the drop down does not close immediately after selecting the item. You have to click once again on the item to select & choice the drop down.
If you observe the same then the bug is reproduced.

Even i have added the mouseListener to the choice. clicking on the choice triggers only mousePressed event not the mouseReleased event.

This works fine in Mustang b105, Even it works fine in jdk7.0 b01 build , but fails in jkd7.0 b02 onwards. Hence this is a regression.
i tested this in vista ulitmate b6000.

Comments
EVALUATION

As it was described in previous evaluation, in some cases the mouse messages are consumed. It's not a good idea to consume the mouse messages. It's better to skip the messages instead of to consume it. In this cases ::DefWindowProc(WM_LBUTTONUP) call properly processes the messages.
2007-06-28 
EVALUATION

There is known Windows bug (4338368):

On Windows XP native system triggers spurious WM_LBUTTONUP messages
when user transfers focus from choice component to another component
using TAB key.

This bug has been workarounded:

"override WmKillFocus and WmMouseUp in awt_Choice.cpp to keep track
of these events and consume extra event right after it was triggered"

Hovewer, the bug is not reproducible on Vista. Nevertheless, according
to the workaround we consume every next WM_LBUTTONUP event for choice :(
2007-01-30


Hardware and Software, Engineered to Work Together