Need Keyboard event path to be Unicode Internally

VERIFIED FIXED in M6

Status

()

Core
Event Handling
P3
normal
VERIFIED FIXED
19 years ago
19 years ago

People

(Reporter: tague, Assigned: joki (gone))

Tracking

Trunk
All
Windows NT
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

19 years ago
The input path for Seamonkey needs to be Unicode Internally.  We need the
XPWidget/XPToolkit code to map between native platform events and Unicode for
keyboard input (see bug #4819) and we need the DOM/Core group to provide a
Unicode clean in the areas of event flow that they own.

The International group will be providing an adapter layer to map between the
native platform character set and unicode.  We need the DOM/Core group to
provide access to thheir module through APIs which take Unicode character
data, and we need them to make sure that the internal data path is Unicode
clean.

See related bug #4816, #4817, #4819
(Assignee)

Comment 1

19 years ago
Could you be a bit clearer on what you need from us here?  Access to the DOM
should be through DOM api's which provide data in Unicode format.  So what's
the problem?
(Reporter)

Comment 2

19 years ago
I've been asked to break some of the event handling bugs into two pieces since
part of them belong to the Gecko/Core/DOM group and part of them belong to the
XPWidget/XPToolkit areas, so that we can track responsibility for deliverables
against both groups.

Currently the DOM API's provide Unicode access, but they are not completely
Unicode clean since I can only type in the ASCII range of characters - there is
no support for extended characters found in European languages.

Updated

19 years ago
Target Milestone: M5

Comment 3

19 years ago
Blocker for M5 IME deliverable.

Updated

19 years ago
Target Milestone: M5 → M6

Comment 4

19 years ago
Moving off M5 radar since Tom is out of town.
(Reporter)

Updated

19 years ago
Status: NEW → RESOLVED
Last Resolved: 19 years ago
Resolution: --- → FIXED
(Reporter)

Updated

19 years ago
Status: RESOLVED → VERIFIED
(Reporter)

Comment 5

19 years ago
This was fixed in M5.  Moving to verified since its a code/design issue.
You need to log in before you can comment on or make changes to this bug.