Closed
Bug 18986
Opened 25 years ago
Closed 25 years ago
Tab key doesn't work on single extended char in form fields
Categories
(Core :: Internationalization, defect, P3)
Tracking
()
VERIFIED
FIXED
M12
People
(Reporter: blee, Assigned: ftang)
References
()
Details
Steps to reproduce: 1) Load the page in URL above. 2) Switch on EN KB (if non-EN OS). 3) Type an extended char (e.g., Alt+0198: Æ) in a Client ID field and hit Tab key. ==>Cursor doesn't move to the next field, it disappears instead. If another extended char is typed in, the Tab key behaves correctly. Tab works when even number of extended char's are typed in (but not odd number). As suspected, it works with a single CJK (DB) char and single low ASCII char. Win32 specific (bld: 11-15-21-M11). Doesn't happen in Mac.
Assignee | ||
Updated•25 years ago
|
Status: NEW → ASSIGNED
Target Milestone: M12
Assignee | ||
Updated•25 years ago
|
Status: ASSIGNED → RESOLVED
Closed: 25 years ago
Resolution: --- → FIXED
Assignee | ||
Comment 1•25 years ago
|
||
Fix it after remove not needed IME_FROM_CHAR code.
Comment hidden (collapsed) |
You need to log in
before you can comment on or make changes to this bug.
Description
•