257013 - Repeated Input Codes and Characters are not solved yet.

Status: RESOLVED EXPIRED

(MailNews Core :: Composition, defect)

Description

[Timothy Huang]

User-Agent:       Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8a3) Gecko/20040825
Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8a3) Gecko/20040825

This late build solved partial bug I reported several days ago. However, it does
not full solve the problem. Please see the screen shot.

Reproducible: Always
Steps to Reproduce:
1. Open the mail composer
2. Input some Chinese characters
3. Input codes and the target Chinese characters are repeated.

Actual Results:  
Input codes and the target Chinese characters are repeated.

Expected Results:  
This is a very serious problem rendering the normal function of the mail
composer as well as entering Chinese in any webpage.

Just a guess -- somehow the current builds grabed the input code field too
early. On the Mac, as far as I know, the input codes shall not be accessible to
the application -- only the target Chinese characters shall be available.

I am kind of interested on how this is accomplished, because there is such a
need in developing some very useful and interesting Chinese applications.

Comment 1

[Timothy Huang]

Attachment: Screen shot of Still not fix yet.

Please read the text, both English and Chinese, on the screen shot. It shows
the problem.

Comment 2

[Mike Cowperthwaite]

Not a blocker:
  http://bugzilla.mozilla.org/bug_status.html#severity

(In reply to comment #0)
> This late build solved partial bug I reported several days ago. 

Which bug was that?


> Input codes and the target Chinese characters are repeated.

I looked at that screenshot.  Do you mean that you only entered four Chinese 
characters, but the program acted as if 33 were entered?

Comment 3

[Gervase Markham [:gerv]]

This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/

Comment 4

[Gervase Markham [:gerv]]

This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.