310634 - Ctrl [+ Shift] + right arrow does not behave correctly

Status: RESOLVED INCOMPLETE

(Thunderbird :: Message Compose Window, defect)

Description

[Andy Holaday]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.12) Gecko/20050915 Firefox/1.0.7
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.12) Gecko/20050915 Firefox/1.0.7

When a message contains mixed font styles (e.g., size, underline, italics, font
changes), using Ctrl + right arrow, the cursor moves beyond the next word. If
selecting text using Ctrl + Shift + right arrow, the selection grabs more than
the next word.

Reproducible: Always

Steps to Reproduce:
1.Compose a message with mixed font elements. Try italics, bold, in/decreased
font size or a font change.
2.Use Ctrl + right arrow to navigate or Ctrl + Shift + right arrow to select
words inserted before a change in the font style.

Actual Results:  
The cursor will usually move to the second word beyond the style change. In some
cases (font size changes), the cursor may move three words to the right. 

Expected Results:  
The cursor should only move to the beginning of the word following the first
space after the current word when using Ctrl [+ Shift] + right arrow.

No themes used.

Using Ctrl [+ Shift] + left arrow instead of right arrow always moves the cursor
to the expected place.

Comment 1

[Adam Guthrie]

Same problem as in bug 265797?

Comment 2

[Andy Holaday]

(In reply to comment #1)
> Same problem as in bug 265797?

Perhaps it is related in some way, but I don't see it as the same issue?

Bug 265797 has different issues concerning selections, and was linked to an
extension. Though I agree with the author of bug 265797 that an apostrophe
should be treated as part of a word, that is not the issue I am reporting here. 

FWIW I have no TB extensions installed.

Comment 3

[Gary Kwong [:gkw] [:nth10sd] (NOT official MoCo now)]

Reporter, does the issue still occur in the latest supported 2.0.0.x / Shredder trunk nightlies?

(1.5.0.x is now end-of-life and the latest supported 2.0.0.x is 2.0.0.16)

Comment 4

[Joshua Cranmer [:jcranmer]]

RESO INCO per lack of response to last question. If you feel this change was made in error, please respond to this bug with your reasons why.