Closed
Bug 7538
Opened 25 years ago
Closed 25 years ago
Editor: Editing text munges high ASCII characters
Categories
(Core :: DOM: Editor, defect, P3)
Tracking
()
People
(Reporter: cpratt, Assigned: mozeditor)
Details
build id: 1999060208 platform: windows nt to reproduce: open an Editor window and type something that includes high ASCII. I typed "Schön daß Du da bist". Then, go ahead and click somewhere else in the document, click back into that sentence, type something & backspace (I can't say for sure WHAT needs to be done exactly to reproduce this). What I then see instead of what I typed is "Schn da* Du da bist" where * represents a weird glyph that looks kind of like two upside-down "A"s on the top of a fraction with and upside down "IIS" on the bottom.
I believe this is a duplicate of the nsString2 bug Joe and Simon already found and fixed. Assigning to Joe, cc simon and rickg.
Updated•25 years ago
|
Status: NEW → RESOLVED
Closed: 25 years ago
Resolution: --- → DUPLICATE
Comment 2•25 years ago
|
||
This is more likely due to our complete inability to handle non-ASCII text, and as such is a dup of bug 6208 *** This bug has been marked as a duplicate of 6208 ***
Comment 3•25 years ago
|
||
Here's one sure way to reproduce this problem. 1. Start the editor or Mail composer 2. Pick a new line to start inserting characters. 3. Now input some non-ASCII Latin 1 characters -- cpratt's example will do. 4. Now, press CR. This will cause the problem orginally reported by cpratt. Whta you see there seems to be a Korean character. 5. Go back to the line in step 4 and add some more accented Latin 1 characters. Now try pressing the CR. This time the problem will not occur again.
Comment 4•25 years ago
|
||
By the way this is not a general Latin 1 high-bit range input failure. They can be input and maintained if you don;t perform certain actions -- at least one example is mentioned here.
Comment 5•25 years ago
|
||
If you see high-ascii characters change *when you hit the return key*, then that should be fixed by the fix for bug 7479. The fix went in today.
You need to log in
before you can comment on or make changes to this bug.
Description
•