The edit cursor and the content being edited does not match when encounter specific string(with Chinese)(from Word doc file)



15 years ago
13 years ago


(Reporter: Arthur Tsai, Unassigned)



Windows 2000

Firefox Tracking Flags

(Not tracked)




15 years ago
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; zh-TW; rv:1.5) Gecko/20031007 Firebird/0.7
Build Identifier: Mozilla 1.5  - Released October 15, 2003

When I am editing a HTML file and encouter a specific string, the problem occurs.

It would be like that there is an invisible edit cursor, which does all my edit

one character "forward" of the edit cursor I really see.
The problem is limited to "one row". It does not affect other rows, wheather the
line is 

broken by wrapping or hard return.

The specific string is this:
(The english translation is "Rippley says")

It contains some Chinese characters. But the charset or encoding of Composer is
Simply input this string causes no problems.
This string is problematic if it's originally copied from a doc file(Word97),
and be pasted to Composer.
The problematic string copied and pasted within Composer causes problem, too.

I also found a strange thing about the string:
If I place the "visible cursor" between "»¡" and ":", and type "a", the
"invisible cursor" would give " a" before "»¡", like this:
·ç´¶²ú a»¡:¡¨
If I delete the strange "space", the string would become normal, no longer cause
any problems.

Reproducible: Always

Steps to Reproduce:
1.put in the problematic "·ç´¶²ú»¡:¡¨"
2.type "1245" after it(the problem may occure in this step already) cursor between "2" and "4"
4. type "3"

Actual Results:  

Expected Results:  

Simply input this string causes no problems.
This string is problematic if it's originally copied from a doc file(Word97),
and be pasted to Composer.


15 years ago
Blocks: 229259

Comment 1

15 years ago
I'm gonna take a look later on Windows.
Keywords: intl
Product: Browser → Seamonkey
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:
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.
Last Resolved: 13 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.