Closed Bug 269286 Opened 20 years ago Closed 20 years ago

Ctrl+arrow keys not working in message compose window in 0.9

Categories

(Thunderbird :: Message Compose Window, defect)

x86
Windows XP
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: jay911, Assigned: mscott)

Details

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0

In TB 0.8, when composing a message, one can navigate a word at a time through
previously entered text in the message body using Ctrl+left and Ctrl+right. This
has disappeared in 0.9 - I have 0.9 on one machine and 0.8 on another and can do
the described behavior in each.

Reproducible: Always
Steps to Reproduce:
1. Open a new compose window.
2. Type any amount of text >= 2 or more words in length.
3. Press Ctrl+Left

Actual Results:  
Cursor remains at end of typed text.

Expected Results:  
Cursor should have moved to the beginning of the current word (immediately after
the last space in the string).

Same extensions installed in both Thunderbird setups (0.8 and 0.9) - don't think
any of them would have anything to do with this behavior.
After re-reading my initial description, I should clarify.

My machine that has 0.9 on it can NOT navigate through text with Ctrl+arrows.
My machine that has 0.8 on it CAN navigate through text with Ctrl+arrows.

In other words it looks like the functionality was dropped somehow in the 0.9
version.
See bug 262550 comment 2 -- do you have any extensions installed which might 
cause this interference?
My apologies - I thought I had tried this with all my extensions disabled
already, but when I just tried it again now with them all disabled, now the
ctrl+arrows work. I'll work at hunting down the errant extension and deal with
it that way.
=>WFM per comment 3
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.