178352 - Shift TAB does not return to Address fields from subject or body

Status: RESOLVED WORKSFORME

(MailNews Core :: Composition, defect)

Description

[Ross Lindell]

User-Agent:       Mozilla/5.0 (Macintosh; U; PPC Mac OS X; en-US; rv:1.2b) Gecko/20021103
Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X; en-US; rv:1.2b) Gecko/20021103

Whether replying or composing new, once the Address field is left via RETURN key
or TAB key, shift TAB does not go back to Address field.

Reproducible: Always

Steps to Reproduce:
1.  Open A new Mail message, or reply to a Mail message.
2.  Once addressed, proceed to Subject or Body of message
3.  Hit SHIFT-TAB twice.

Actual Results:  
Cursor sits in Subject field.

Expected Results:  
First SHIFT-TAB and Cursor should move to Subject, and second SHIFT-TAB then to
Address fields.

TiBook, OS 10.2.1

Comment 1

[Jean-Francois Ducarroz]

-->varada

Comment 2

[Greg K.]

Confirmed using FizzillaCFM/2002103011 on 10.1.5.

Comment 3

[R.K.Aa.]

*** Bug 179842 has been marked as a duplicate of this bug. ***

Comment 4

[(not reading, please use [e-mail] instead)]

taking all of varada's bugs.

Comment 5

[Kathleen :Brade]

duplicate of bug 87321?

Comment 6

[Kathleen :Brade]

*** Bug 187986 has been marked as a duplicate of this bug. ***

Comment 7

[Michael Baffoni]

I'm seeing this on Mozilla 1.8a
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8a) Gecko/20040418 in
Windows, but worked fine on Mozilla 1.6, 1.7a, 1.7b.

Comment 8

[Wayne Mery (:wsmwk)]

Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8a6) Gecko/20041128
and Thunderbird version 0.6+ (20041115)

I believe bug 265582 is a dup of this.

Current behavior for me is [shift] [tab] works in subject, i.e. it jumps back to
an empty address field.

But when cursor is positioned on ANY line at the START of the line, then back
tab does not work to jump back to subject.

is bug 240504 related (or bug 27932) ?

(this sort of brings back bad memories of a bug that would crash moz if you back
tabbed from one address field to another)

Comment 9

[Mike Cowperthwaite]

(In reply to comment #8)
> I believe bug 265582 is a dup of this.

As mentioned there: no, it's not.  That bug is easily demonstrated as a 
regression between 1.7 and 1.8 builds, this is older than that.

Marking this WFM, as it's an ancient bug and I haven't seen the symptom myself.
If I'm mistaken, then whoever is still seeing this is welcome to reopen it.