138593 - keyboard navigation is flakey

Status: VERIFIED WORKSFORME

(MailNews Core :: Composition, defect)

Description

[Michael Baffoni]

RC1 seems to be really bad at keeping track of cursor location when using
tabs/returns.  Intermittantly, I get into a state (after using Moz for a while),
where clicking return on an address does not advance the cursor to either the
next line or the subject field.  While in this state, hitting tab does not go to
subject and then to body, it goes other places.  On one email I was composing,
tab went from to: line, to the first email addres (such and such [e-mail]
wrote:) and I would know it was there because it would put a light dotted box
around it, and successive tabs would go to the next email address, etc. 
Stopping Moz and restarting would (temporarily) fix this.
Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.0rc1) Gecko/20020417

Comment 1

[Michael Baffoni]

Ran into this bug again - I think it may be related to auto-complete.  I typed
in an address (my own) that should have resolved, but it didn't.  I hit return
and it wouldn't go to the next TO: line, it would just stay there.  I could use
the mouse to click into the subject line, click into the body and type, but if I
clicked into the first TO: line, all I can do is higlight/edit the first line. 
If I put in an address into the first to line, and click send, it gives me the
error that I can't send because there is no address in the email.  Opening a new
email does not have this error.  

Comment 2

[Jean-Francois Ducarroz]

-->varada

Comment 3

[John Levon]

Can you reproduce the problem with a current Mozilla build ?

Comment 4

[Michael Baffoni]

I'm not sure if it is the same reason, (this bug is kind of old), but I know
that with the 2002101108 build, after hitting tab from the subject line, the
cursor doesn't show, but when you start typing, it eats the first charactar you
typed, then jumps into the .sig portion of the email (of a reply).  In fact,
there is no .sig on a new compose message, but it eats the character (and jumps
down one line) just like the reply does.

Comment 5

[Mike Cowperthwaite]

Michael Baffoni, are you still experiencing either the original problem or the 
one from comment 4?  Have you upgraded to a current Mozilla build (1.3 or 1.4)?

The latter problem sounds similar to bug 160702 or bug 166278.

Comment 6

[Michael Baffoni]

Forgot about this bug.  Works for me on latest nightly 2003060608.

Comment 7

[Mike Cowperthwaite]

v wfm