Note: There are a few cases of duplicates in user autocompletion which are being worked on.

{feature} Need extensions to transaction manager to support Japanese Input

VERIFIED FIXED in M6

Status

()

Core
Editor
P3
major
VERIFIED FIXED
19 years ago
16 years ago

People

(Reporter: tague, Assigned: kinmoz)

Tracking

Trunk
All
Windows NT
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

19 years ago
To correctly support Japanese input, I want to be able to create a secondary
transaction "stack" which can't interact with the main transaction stack of the
application, to represent the changes that occur while an input method is being
used.  I attempted to use the batching features - but the batching functions do
not support transactions in the style that I need.

Let's say I've typed ABC into the editor, and now I engage the input method by
selecting it from the keyboard menu.  I type kakikukeko and then <return> to
signal that I am done with the input method.  While I am typing with the input
method engaged - I can't completely commit the changes that I am typing into
the main editor buffer until the <return> key is pressed.  The kakikukeko
string needs to be editable independent (and unable to affect) the string ABC.
Once I hit return, the transaction manager needs to create a new transaction
which represents inserting the entire string kakikukeko into the text buffer as
an atomic insert.

Please contact for more details and explaination about what I need.  It's
difficult to describe in a bug report, but I can demonstrate how this needs to
work in person.

Updated

19 years ago
Assignee: kostello → kin
Summary: Need extensions to transaction manager to support Japanese Input → {feature} Need extensions to transaction manager to support Japanese Input
Target Milestone: M5

Comment 1

19 years ago
Changing this to a feature request and assigning this to Kin. Let's discuss this
in our team meeting.
(Reporter)

Updated

19 years ago
Target Milestone: M5 → M4
(Reporter)

Comment 2

19 years ago
Greg :-  This is something I need to complete work scheduled for the M4
milestone.
(Assignee)

Updated

19 years ago
Status: NEW → ASSIGNED
Target Milestone: M4 → M5
(Assignee)

Comment 3

19 years ago
Changed status to assigned and the milestone to M5.
(Assignee)

Updated

19 years ago
Target Milestone: M5 → M6
(Assignee)

Comment 4

19 years ago
Changed milestone to M6.
(Reporter)

Updated

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

Comment 5

19 years ago
This should have goten fixed with the work we did in M5.  I'm moving it to
verified since it's a code/design issue.
(Reporter)

Updated

19 years ago
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.