Closed Bug 298136 Opened 20 years ago Closed 19 years ago

Left-Arrow and Right-Arrow keys ignored in Compose window

Categories

(Thunderbird :: Message Compose Window, defect)

x86
Linux
defect
Not set
blocker

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: wsheets, Assigned: mscott)

Details

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8b2) Gecko/20050618 Firefox/1.0+
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8b2) Gecko/20050618 Firefox/1.0+

thunderbird(HEAD):  for the last two days I have been unable to use the L/R arrow
keys while composing a message.  The only way I can move the cursor while
composing a message is to left-click the mouse where I want the cursor to be.

The 'Backspace' key and the Up/Down arrows work properly.  Curiously, Ctl-H
does *not* work to delete a char.

NOTE:  this bug does *not* apply to Firefox(HEAD) or mozilla(HEAD)!

Reproducible: Always

Steps to Reproduce:
1.Click on the Write icon to compose a new message
2.Start typing anywhere in the To, Subject, or Body windows.
3.Try to move the cursor with Left/Right arrow keys, and fail.
Actual Results:  
The cursor ignores the Left/Right arrow keys.

Expected Results:  
The cursor should move left or right, as it always has until the last two days or 
so!  I emphasize again: Firefox(HEAD) and mozilla(HEAD) are *not* affected by
this recent bug.
<sigh>  After many adventures I discovered that deleting my ~/.thunderbird
and re-importing my mozilla settings completed cured this 'bug'  :o/

I think you can mark this WFM or 'imaginary bug'.

I'd really love to understand how the contents of my ~/.thunderbird
directory could cause this strange cursor behavior.

Any ideas?

Thanks, and sorry for the noise.  I am very grateful for the hard
work that everyone donates to this project!

I'd like to say that I suffered similar problems in Windows. Although I am
unsure what caused it, I was unable to do any cursor movement, cutting, pasting,
etc with the keyboard while using Thunderbird 1.0.6. Re-installing solved the
problem.
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.