Closed
Bug 865566
Opened 12 years ago
Closed 12 years ago
Separator key on NumPad of Brazilian keyboard should cause "Separator" key value
Categories
(Core :: Widget: Win32, defect)
Tracking
()
RESOLVED
FIXED
mozilla23
People
(Reporter: masayuki, Assigned: masayuki)
References
Details
(Keywords: intl)
Attachments
(1 file)
|
(deleted),
patch
|
jimm
:
review+
|
Details | Diff | Splinter Review |
According to <http://blogs.msdn.com/b/michkap/archive/2006/10/07/799605.aspx>, Separator key on Numpad of Brazilian keyboard causes VK_ABNT_C2 instead of VK_SEPARATOR. We should map it to "Separator" for KeyboardEvent.key.
I ordered Brazilian keyboard. I'll work on this after it comes.
|
Assignee | |
Comment 1•12 years ago
|
||
Ugh, different Brazilian keyboard comes today :-(
Therefore, I couldn't test this patch with actual Brazilian ABNT keyboard.
However, fortunately, Japanese keyboard for Mac has "separator" key. And with it, I confirmed that Windows 8 uses VK_ABNT_C2 (0xC2) for it. And I can input "." by the key only when I select Portuguese of Brazil. So, I think that this patch works fine with actual Brazilian keyboard.
Attachment #743681 -
Flags: review?(jmathies)
|
||
Updated•12 years ago
|
Attachment #743681 -
Flags: review?(jmathies) → review+
|
|
Assignee | |
Comment 2•12 years ago
|
||
Status: NEW → ASSIGNED
|
||
Comment 3•12 years ago
|
||
Status: ASSIGNED → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla23
|
||
Comment 4•11 years ago
|
||
Just in case you did not see my comment on https://bugzilla.mozilla.org/show_bug.cgi?id=833719#c56 yet. There are TWO “extra” keys on the Brazilian keyboard: C1 and C2.
AFAIU, C1 is much more important than C2. Can you find a DOM code to map it to (since 0xC1 is, apparently, occupied)?
You need to log in
before you can comment on or make changes to this bug.
Description
•