Closed Bug 2914 Opened 28 years ago Closed 25 years ago

[IME/rule?txn?]IME- Undo of Japanese text works incorrectly in Mail address field

Categories

(MailNews Core :: Internationalization, defect, P2)

PowerPC
All
defect

Tracking

(Not tracked)

VERIFIED INVALID

People

(Reporter: nhottanscp, Assigned: ftang)

References

Details

(This bug imported from BugSplat, Netscape's internal bugsystem. It was known there as bug #80317 http://scopus.netscape.com/bugsplat/show_bug.cgi?id=80317 Imported into Bugzilla on 02/04/99 16:31) 1) Type English text "aaa" 2) Type Japanese any Japanese text 3) Undo by command-z 4) English text "aaa" is removed instead of Japanese text Encoding setting doesn't affect the result. In body text filed, undo doesn't work at all after input Japanese text.
Assigning to ftang, because I don't have a Japanese system.
Kathy, this is a UNDO problem in editor. nhotta and I do not understand how we do UNDO in editor....
This happens with text input through 2-byte input methods (PIM, Kotoeri, etc.) regardless of the script - also happens with Roman(1byte/2byte) input via PIM or Kotoeri under Asian or Western encoding. Ditto in English version Communicator.
ftang, naoki and I decided this won't get fixefor 4.x release since latin characters have problems with undo (non-composer fields). I am reassigning to naoki (nhotta) since this will probably fall to him to fix (I'm guessing that it's the I18N stuff in VText that will need some work)
This happens in HTML composer, too. Undo of Japanese text works fine in Plain text mail.
Kathy, Please check bug #67508 I wrote a comment about current TSMTE implementation. Naoki
As this is related limitation of TSMTE support, I may not be able to fix everything. I will post a description of possible fix later.
The current version of 5.0 (source331) ignores the Japanese input for undo. It used to mix up ascii input and Japnese input in undo so there is a improvement. Once Metrowerks PowerPlant merge TSM support then undo should be supported uniformly through single byte to multibyte input. This bug will not targeted to 4.1 and 4.5.
OS: All
QA Contact: 1308
Assignee: nhotta → tague
Status: ASSIGNED → NEW
Target Milestone: M5
This bug is for Gromit not SeaMonkey. However, we need to remember we can do Undo correctly on Mac when we implement IME support. Reassign this to tague and set the target to M5.
Status: NEW → ASSIGNED
Summary: Undo of Japanese text works incorrectly in Mail address field → IME- Undo of Japanese text works incorrectly in Mail address field
Target Milestone: M5 → M9
I'm moving this bug out to M9. This is a 4.x bug, this functionality isn't even implemented yet in SeaMonkey - hardly a M5 candidate. This is an advisory bug, so I'm moving it out as far as I can at the moment.
Depends on: 6262
need ender as *thee* text widget before i can fix this
Is this a Mac only bug? If so, pls add [PP] to the summary line.
moving to M10 to reflect bug fixing priorities
Target Milestone: M10 → M11
moving to m11, since still waiting on dependency.
Blocks: 11091
(product is MailNews and target milestone is M11 or M12 - add to mail beta tracking bug)
Blocks: 15693
Assignee: tague → ftang
Status: ASSIGNED → NEW
reassign to ftang per i18ngrp reassignment meeting.
Target Milestone: M12 → M11
Status: NEW → ASSIGNED
Priority: P3 → P2
Summary: IME- Undo of Japanese text works incorrectly in Mail address field → [IME/rule?txn?]IME- Undo of Japanese text works incorrectly in Mail address field
Naoki, could you try this on Window also. I believe this is a ALL bug but not a Mac bug. Is that correct ?
Blocks: 16127
Status: ASSIGNED → RESOLVED
Closed: 25 years ago
Resolution: --- → INVALID
This bug was filed when we were using VText so this is not valid after 4.5. In 5.0, multiple level Undo is working. If you type Ascii, Japanese then Ascii again, you can Undo three times. Redo doesn't seem to be working but that's not Japanese specific. So I mark this bug as invalid.
Status: RESOLVED → VERIFIED
Verified as Invalid for Mozilla.
Product: MailNews → Core
Product: Core → MailNews Core
You need to log in before you can comment on or make changes to this bug.