Bug 79190 - [consistency] missing Button KeyDown events
Summary: [consistency] missing Button KeyDown events
Status: CLOSED WONTFIX
Alias: None
Product: Platform
Classification: Eclipse Project
Component: SWT (show other bugs)
Version: 3.1   Edit
Hardware: PC Windows 2000
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Grant Gayed CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords: consistency
Depends on:
Blocks:
 
Reported: 2004-11-22 10:26 EST by Grant Gayed CLA
Modified: 2019-09-04 01:55 EDT (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Grant Gayed CLA 2004-11-22 10:26:25 EST 
- run the ControlExample, stay on the default Button tab
- listen for KeyDown and KeyUp
- give focus to an example Button on the page
- press Enter
  -> on motif, gtk and mac you'll get a KeyUp but no preceding KeyDown (somehow 
eaten in the traversal?)
  -> on win32 you'll get neither, but this seems less shady than getting a 
KeyUp without a preceding KeyDown
Comment 1 Steve Northover CLA 2004-11-22 18:50:05 EST 
It seems the Windows behavior is wrong.  The key down should be eaten by 
traversal but the key up will still come through.  Need to check other 
traversal keys.
Comment 2 Steve Northover CLA 2004-11-24 15:20:46 EST 
Windows is wrong because "lastKey" is cleared inside of Display when a 
successful traversal occurs.  This seems wrong.  I need to think about it for 
a while.
Comment 3 Steve Northover CLA 2005-01-19 19:49:26 EST 
Grant to prioritize.
Comment 4 Lars Vogel CLA 2019-09-04 01:55:20 EDT 
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it and remove the stalebug whiteboard tag. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--