Closed Bug 60851 Opened 25 years ago Closed 24 years ago

Windows Keyboard buttons not working

Categories

(Core :: DOM: UI Events & Focus Handling, defect, P3)

x86
Windows 2000
defect

Tracking

()

VERIFIED DUPLICATE of bug 64371

People

(Reporter: xraytwo, Assigned: vishy)

Details

From Bugzilla Helper: User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; m18) Gecko/20001120 BuildID: 2000112020 The internet browsing keyboard buttons on the Microsoft Natural Pro/Internet keyboard does not seem to function comprared to working with the previous 4x version of navigator Reproducible: Always Steps to Reproduce: If possible, test using the Microsoft Natural Keyboard Pro/USB's internet buttons- back, foward, stop, refresh, etc Actual Results: Nothing happened Expected Results: They buttons should work like the browser buttons
I'm sure this is a bug so I'm confirming it; it may even be a duplicate. I know that there is a Sun equivalent (certain keys on keyboard don't work).
Status: UNCONFIRMED → NEW
Ever confirmed: true
Summary: Keyboard buttons not working → Windows Keyboard buttons not working
Since Don has left, Vishy is taking his bugs in bulk, pending reassignment. thanks, Vishy
Assignee: don → vishy
In order to implement this we need to process WM_APPCOMMAND messages that specify any of the APPCOMMAND_BROWSER_* values. See http://msdn.microsoft.com/library/psdk/winui/mousinpt_8sbo.htm . WM_APPCOMMAND is not defined in default VC6 installations, so you'll have to install the latest Platform SDK and #ifdef the new code.
Blocks: keydead
No longer blocks: keydead
Marking this as a dupe of Bug 64371, since it has a better discussion of the topic.
resolve for Chris Lyon *** This bug has been marked as a duplicate of 64371 ***
Status: NEW → RESOLVED
Closed: 24 years ago
Resolution: --- → DUPLICATE
mass verification of duplicate bugs: to find all bugspam pertaining to this, set your search string to "DuplicateBugsBelongInZahadum". if you think this particular bug is *not* a duplicate, please provide a compelling reason, as well as check a recent *trunk* build (on the appropriate platform[s]), before reopening.
Status: RESOLVED → VERIFIED
Component: Keyboard: Navigation → User events and focus handling
You need to log in before you can comment on or make changes to this bug.