Red Hat Bugzilla – Bug 441255
Incorrect positioning of cursor at end of message while composing
Last modified: 2018-04-11 02:55:11 EDT
Description of problem:
Under the correct conditions, cursor is positioned wrong when using the END key
to position to end of last line in message. Other strange end of message
behaviors also occur. Believe this is related to bug 292580 at
bugzilla.mozilla.org which was originally posted 2005-05-01 and still has status
Version-Release number of selected component (if applicable):
Also observed in earlier versions
Every time with this test case
Steps to Reproduce:
1. Create this message, but don't end message with a newline
This is the first paragraph
with a second line.
This is the second paragraph
with another line
append first paragraph here
2. Position cursor at the beginning of the message with:
up up up up up home
3. Copy first paragraph with:
shift-down shift-down ctl-C
4. Position cursor at end of message with:
down down down end
5. Paste first paragraph with:
6. Position cursor using:
up up home down down down end
Cursor positions to paste insert point.
Cursor positioned at end of message.
The key to making this test fail, is the 3rd down in step 6. This attempts to
position the cursor beyond the end of the message. If you watch carefully, the
screen updates after this down, which would indicate something unusual happened
in the code here. The other key is to not ever end the message with a newline,
or this extra down keystroke will not cause a problem.
While there have been lots of speculation of the cause of this elusive problem
in the bug mentioned above, it would appear to be a simpler case of improper end
of buffer marking after paste or other operations. Fiddling with the cursor will
eventually cause Thunderbird to figure out the new end of buffer.
I am afraid that after all it will be better to let this bug be resolved
upstream. We don't have enough capacity to deal with it, so it would probably
stay rotenning here forever (or until closed as obsolete). Moreover, thunderbird
upstream community seems to get into second chance mode and I see them fixing
very old bugs where I have lost my hope to have them fixed.
Red Hat will continue to track the issue in the centralized upstream bug
tracker, and will review any bug fixes that become available for consideration
in future updates.
Thank you for the bug report.