After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 239157 - Reversed text in body of composer window after inserting HTML file
Reversed text in body of composer window after inserting HTML file
Status: RESOLVED DUPLICATE of bug 244200
Product: GtkHtml
Classification: Other
Component: Editing
unspecified
Other All
: Normal major
: ---
Assigned To: gtkhtml-maintainers
Evolution QA team
evolution[composer] evolution[HTML]
Depends on:
Blocks:
 
 
Reported: 2003-03-06 00:39 UTC by C. Pruden
Modified: 2003-07-02 16:47 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description C. Pruden 2003-03-06 00:39:34 UTC
Description of Problem:

Any time after a HTML file is inserted into the body of a message being
composed, the cursor then outputs the typed in text backward.


Steps to reproduce the problem:
1. From Evolution Applicatoin, select File -> New -> Mail Message
2  From the new "Compose a message" window, select Insert -> HTML File...
3. Insert a HTML file on local disk
4. After inserting the HTML file, go to the top of the inserted HTML in the
composer window and any new text added is typed out backwards. Ie. forward
= "test", backwards = "tset"

Actual Results:
new text spelled backwards

Expected Results:
any new text should output in a forward fashion

How often does this happen? 
Every time. However, depending on how you navigate to the top of the
inserted HTML with the up arrow key on the keyboard, you may get a "normal"
cursor back that allows for forward flowing text comments to be added to
the message.

Additional Information:
Any text added at the bottom of the inserted HTML is typed correctly
Comment 1 Gerardo Marin 2003-06-20 15:57:39 UTC

*** This bug has been marked as a duplicate of 244200 ***
Comment 2 Larry Ewing 2003-07-02 16:47:20 UTC
can you attach example html that causes this problem?