On Solaris, physical F11 and F12 keys do not map to VK_F11 and VK_F12

RESOLVED FIXED

Status

()

Core
Keyboard: Navigation
RESOLVED FIXED
16 years ago
3 years ago

People

(Reporter: Jay Yan, Assigned: Jay Yan)

Tracking

(Blocks: 1 bug)

Trunk
Sun
SunOS
Points:
---
Dependency tree / graph

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(1 attachment)

930 bytes, patch
Akkana Peck
: review+
blizzard
: superreview+
Judson Valeski
: approval+
Details | Diff | Splinter Review
(Assignee)

Description

16 years ago
In Sun's keyboard, when key F1 to F10 are pressed, keycode F1...F10 are
generated, but when key F11 is pressed, keycode SunF36 is generated instead of
F11: (Seen from the output snip of xev, the keycode is SunF36)

*************************
KeyPress event, serial 23, synthetic NO, window 0x9800001,
    root 0x37, subw 0x0, time 1712315695, (76,-9), root:(192,165),
    state 0x0, keycode 16 (keysym 0x1005ff10, SunF36), same_screen YES,
    XLookupString gives 1 characters:  ""

KeyRelease event, serial 23, synthetic NO, window 0x9800001,
    root 0x37, subw 0x0, time 1712315804, (76,-9), root:(192,165),
    state 0x0, keycode 16 (keysym 0x1005ff10, SunF36), same_screen YES,
    XLookupString gives 1 characters:  ""
***********************************

But when key Stop is pressed, keycode F11 is generated, please see the output
snip of xev:
***********************************

KeyPress event, serial 21, synthetic NO, window 0x9800001,
    root 0x37, subw 0x0, time 1712255010, (340,230), root:(456,404),
    state 0x0, keycode 8 (keysym 0xffc8, F11), same_screen YES,
    XLookupString gives 0 characters:  ""

KeyRelease event, serial 21, synthetic NO, window 0x9800001,
    root 0x37, subw 0x0, time 1712255010, (340,230), root:(456,404),
    state 0x0, keycode 8 (keysym 0xffc8, F11), same_screen YES,
    XLookupString gives 0 characters:  ""
*************************************



It is the keycode list for some Sun keystroke:

Stop F11
Again F12
Props F13
Undo  F14
Front F15
Copy F16
......
Cut  F20



physical F11 does not map to VK_F11, fullscreen function will not work.
see also bug 57262.

Jay
(Assignee)

Updated

16 years ago
Status: NEW → ASSIGNED
(Assignee)

Comment 1

16 years ago
add akk to cc list
(Assignee)

Updated

16 years ago
Blocks: 127812
Keywords: qawanted
QA Contact: sairuh → nobody
(Assignee)

Updated

16 years ago
Depends on: 136522
(Assignee)

Comment 2

16 years ago
Created attachment 78672 [details] [diff] [review]
patch

Since bug 127812 is duplicated and others are working on that bug, I will fix
this beforehand.

Without "full screen" feature on Linux, it is a little difficult to test it. I
tested this patch in this way:

on my Solaris workspace, I added this line:
<key id="key_fullScreen" keycode="VK_F11" command="View:FullScreen"/>
in file platformNavigationBindings.xul,
and then tested this patch, F11 works.

akk, can you r=? 
thanks
Jay

Comment 3

16 years ago
Comment on attachment 78672 [details] [diff] [review]
patch

Oh, wow, there really isn't a symbol for those keys?  Bummer!  But I'll take
your word for it that they work. r=akkana

Comment 4

16 years ago
Comment on attachment 78672 [details] [diff] [review]
patch

Really marking reviewed this time.
Attachment #78672 - Flags: review+
Comment on attachment 78672 [details] [diff] [review]
patch

sr=blizzard
Attachment #78672 - Flags: superreview+
(Assignee)

Comment 6

16 years ago
checked in.
Status: ASSIGNED → RESOLVED
Last Resolved: 16 years ago
Resolution: --- → FIXED

Updated

16 years ago
Attachment #78672 - Flags: approval+

Comment 7

16 years ago
please checkin to the 1.0.1 branch. once there, remove the "mozilla1.0.1+"
keyword and add the "fixed1.0.1" keyword.
Keywords: mozilla1.0.1+
(Assignee)

Comment 8

16 years ago
checked into branch
Keywords: mozilla1.0.1+ → fixed1.0.1

Updated

16 years ago
Blocks: 163789
Keywords: qawanted
You need to log in before you can comment on or make changes to this bug.