Closed Bug 4390 Opened 26 years ago Closed 25 years ago

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

Categories

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

All
Windows NT
defect

Tracking

()

VERIFIED FIXED

People

(Reporter: tague, Assigned: kinmoz)

Details

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.
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
Changing this to a feature request and assigning this to Kin. Let's discuss this in our team meeting.
Target Milestone: M5 → M4
Greg :- This is something I need to complete work scheduled for the M4 milestone.
Status: NEW → ASSIGNED
Target Milestone: M4 → M5
Changed status to assigned and the milestone to M5.
Target Milestone: M5 → M6
Changed milestone to M6.
Status: ASSIGNED → RESOLVED
Closed: 25 years ago
Resolution: --- → FIXED
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.
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.