Closed Bug 13856 Opened 25 years ago Closed 25 years ago

[pp] some characters not working for type-in

Categories

(Core :: DOM: Editor, defect, P1)

x86
Windows NT
defect

Tracking

()

VERIFIED FIXED

People

(Reporter: buster, Assigned: Brade)

References

Details

(Whiteboard: try in 10/15 build.)

from chofman: Its -double quote -single quote -apostriphy -pound -percent -ampersand -open paren that arent working in mail compose with this mornings release build
Priority: P3 → P1
Target Milestone: M11
chris: what platform(s)? thanks.
win95. 990914 build.
Assignee: buster → brade
assigned to kathy, cc saari. I traced this down a bit and it looks like the key binding code is snarfing up some keys, like the double-quote character. I think this is because ascii char code for double-quote is 39, same as vk_right. either the keybindings are incorrect, or the code is incorrectly cross-mapping keycode and charcode.
Which xul file were you looking at?
I wasn't looking at any xul file in particular, just the default editor code.
the linux build (1999091508) from today doesn't have this problem according to mail/news qa.
works today on win as well. kathy or sujay, if this works on mac please mark it fixed.
Status: NEW → RESOLVED
Closed: 25 years ago
Resolution: --- → FIXED
Summary: some characters not working for type-in → [pp] some characters not working for type-in
this is a windows-specific bug. Marking fixed per steve's comment.
Status: RESOLVED → REOPENED
not working in 9/23 build of Windows....
Resolution: FIXED → ---
Clearing FIXED resolution due to reopen
Blocks: 15693
*** Bug 16047 has been marked as a duplicate of this bug. ***
Status: REOPENED → RESOLVED
Closed: 25 years ago25 years ago
Resolution: --- → FIXED
I believe this has been fixed now that the keyEvent branch has landed.
not fixed in today's build...Kathy did the fix go in today? Maybe I'll see it fixed in tomorrow's build.
Sujay--please check tomorrow's build; the keyevent branch was carpooled today
Whiteboard: try in 10/15 build.
Status: RESOLVED → VERIFIED
verified in 10/18 build.
You need to log in before you can comment on or make changes to this bug.