Currently you can tab among the edit fields, but you can't tab into /out of the body.

Need this for PR1, so I added a note to the Status Whiteboard.

In 4.5, you weren't able to tab outside the body (Do am I right?) but you should be able to tab in the body from the subject field

Fixed and check in.

This is not working using: 1999-11-09-11m11 commercial builds on NT 4.0 and linux 6.0 1999-11-08-08m11 commerical build on mac OS 8.5.1 1. HTML and Plain text composition windows: cannot tab to body. 2. HTML composition window: Should tabbing skip the html formatting toolbar, it currently does not? (It does in 4.x) 3. Should tabbing also have Shift+Tab to reverse order (4.x windows does and in this way you can tab out of the body). 4. Highlighting reflecting the current focus is bad; can't necessarily tell where tab landed you. (probably a separate issue) Reopening...

I don't think this should be a M11 stopper bug.

I'm going to change to M12.

Putting on pdt- radar.

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

This affects aim compose as well. Ccing amusil, lchiang, prass, scalkins

I have a fix that works on Mac but not on Windows (no idea about Unix). My problem is that the tab key doesn't generate onkeyup or onkeydown event on Windows like it does on Mac. I need those events in order to intercept the tab key to do my own action on tab. Reassign to joki for the tab key event issue. Please reassign to me when done.

Moving M14.

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

I've looked at this but its not gonna get figured out for M13

Nominate for beta1

removing pdt- for dogfood.

Tabbing from subject line to body is PDT+ for b1

More tabbing problems: 5. I have to hit Tab/Shift-Tab 2 or 3 times to get from one address field to the next 6. Tab/Shift-Tab should get you also to the To: pulldown and the From: address selector (you can currently only tab between address fields and subject line) Linux build 2000.02.02.09

Putting dogfood in the keyword field.

Reassign to myself, now I correctly key the tab key event on Windows.

done.

What works is that you can now tab from the subject field to the message body. Here's what doesn't work. 1. If you hit TAB in the Subject line, the TAB event goes to the body as well (and the first line is indented). 2. Strange focus problem after hitting TAB in subject line: The caret in the Subject line doesn't go away. Key events go to body (so what you type appears in the body), but cursor key events go to the subject line (so Left, Right make the caret move in the Subject line). 3. Shift-TAB in the subject line takes you to the message body, but it should take you to the last address line. 4. Either it still takes me 2-3 tabs to get from one address field to the next, or I'm tabbing from address field to To: dropdown to next address field. In the latter case, I don't see the dropdown list getting focus, and arrow up/down don't work to choose options. I'm going by the summary here; if you want differen bugs for these issues, let me know. Linux build 2000.02.05.08

some comments: point 1: appends only on linux! we should file a new bug for this one. point 3: should open a new bug, I don't think is a beta or dogfood stopper. point 4: The first tab activate the select object in the next line (which is normal despite that key navigation doesn't work yet in select element), the second tab activate the titled button (I will file a bug for that agains hyatt@netscape.com) and finally the third tab activate the next input field.

I have a fix in my tree that, like with Communicator 4.x, when you hit tab and you are already on the last recipient will not create a new row but instead jump directly into the subject field.

I just filed bug 26912 about point #4.

I've just removed the [PDT+] tag. I think now as the main functionality is there, it's not anymore a dogfood/beta1 issue. Let see what the PDT team has to say.

Putting on PDT- radar.

I have a fix for the problem with the titlebutton taking the focus.

the Title button has been replaced by an image and will not take focus when tabbing from the Select element to the edit field.

Filed bug 27932 for issue (3) and bug 27931 for issue (1). I'm assuming you're working on (2) since you haven't marked this fixed yet.

I am pretty sure already have a bug number for the issue number 2. It's a generic focus problem with text widget.

Point 2 is covered by bug 27936. As all the remainig problem have their own bug, mark this bug fixed.

Using mar09 commercial builds on linux rh6.0, NT 4.0 and mac OS 9.0: Basic tab functionality works in both html and plaintext compose windows, so will mark this bug verified: 1. Tab from address line goes to subject line 2. Tab from subject line goes to message body Outside of the spinoff bugs already mentioned, note there is no keyboard access (by tab or arrow) to the From: (identity) dropdown and no keyboard access to the addressee header types dropdown (To: CC: Bcc:, etc.). I'm not exactly sure what bug #26912 might cover in those areas.

Bug 26912 has now sence here anymore as I replaced the titleButton in the addressing widget by an image. Now when you tab from a recipient field, the cursor jump into the next recipient type popup menu on the next row and if you tab one more time the cursor is now into the next recipient field. If you where already in the last recipient field, pressing tab put the focus into the subjet. Conclusion, ignore bug 26912.

In response to comments above by ducarroz: "Now when you tab from a recipient field, the cursor jump into the next recipient type popup menu on the next row and if you tab one more time the cursor is now into the next recipient field." I do not see this in mar09 builds, there are problems: 1. First tab from existing recipient field doesn't do anything -- you stay in the current recipient field. You never get (apparent) access by keyboard to the next recipient type pop-up as ducarroz mentions; no highlighting, pop-up menu doesn't open, arrow keys don't work to select another header type. 2. Depending on whether the recipient field you're tabbing from is newly entered or previously existing, the second tab will either take you to the subject line or to the next existing recipient line. I am voting for taking the header type and other tabbing/keyboard issues in compose to separate bugs for each issue since this bug is already too too confusing. Adding "basics only" to the summary to clarify what got closed in this bug.

Laurel, could you file a bug for the point number 1. I may already have a fix for part of it but I think key navigation into a select element doesn't work correctly.

Reopening: this hasn't been broken on linux for at least 2-3 weeks. I assumed that there was a bug on that, but this is the only one I could find.

clear target res of M14 since this was reopened.

Putting on [NEED INFO] radar. PDT needs more info. Does this still occur with latest builds? if still a problem, what exactly is it? what is impact to user? Thanks!

Tabbing is totally broken again. To go from one field to another, you have to tab several time (3-4)!

Mass moving M16 to M17 - look for nsbeta2 before anything else.

Putting on [nsbeta2+] radar for beta2 fix.

adding self to cc list. can't tab from subject line to message body in mail compose window with build from 5/30/00 10am.

Putting on [dogfood-] radar since [nsbeta2+] already indicated.

On linux, I still can't tab out of the recipient line into the subject line with one tab (if I hit lots of tabs, it eventually gets there).

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

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

reassigning to varada.

If this isn't fixed by 7/13 we are going to cut from nsbeta2.

marking nsbeta2- as decided by mail triage.

nominate as nsbeta3. It really is annoying that tabbing doesn't work. Using 7-11-09-M17 build. In 4.x I use tab from the addressing field to the Subject field and from the Subject field to the Body ALL the time. Neither of these is currently working.

tab from subject to body got fixed as part of bug http://bugzilla.mozilla.org/show_bug.cgi?id=45926.

Can this bug be closed fixed now? Otherwise, please describe exactly what remains to be fixed. Marking nsbeta3-, tabbing to the body is working.

1. If there is only one line in the addressing widget, it still takes 3 tabs to go from addressing widget to subject line (or back with shift-tab). It should only take 2 (one to the drop down). Bug 26912 was marked fixed, but I don't know if the titledbutton has been converted to the <image> tag in XUL. 2. If there is more than one line in the addressing widget, hitting tab in a line other than the last will make you lose focus (i.e., hitting tab repeatedly never will get you to the next line).

Why should it even take two tabs to get from the addressing field to the subject line? It only took one throughout 4.x (and if you wanted another addressing line, you used return instead of tab). Anyway, three is definitely too many, and is undiscoverable.

I takes two tabs in my Linux 4.7 Communicator (first tab takes you to the "To:" drop-down, next tab to the address field).

Not on any version I've ever used (4.0 through 4.72) -- I just tried it on 4.72: bring up a compose window, type in "akkana<tab>" and the caret starts blinking in the subject field. In fact, there seems to be no way to use the keyboard to get to the "To:" field in 4.x, which admittedly isn't good either. So I can see the argument for wanting the second tab to allow for that (and shift-tab, I assume, would tab to the To field corresponding with the address you just typed in?)

Sorry, I was being stupid. One tab if you're in the last addressing field, 2 going from one addressing line to the next.

Adding ue1 because i felt like it? akin to dveditz@netscape.com's nsbeta2/nsbeta3 keyword mass spams.

This is either WFM or DUP. Basic tabbing works, another bug describes the tabs from addr widget to subject problem.

Which bug is that?

Selmer is referring to bug 49232 for recipient to subj tab. There is also bug 52014 for tab to body problem.

I don't see this bug with Win32 build 2000101008 on Win98. bug 49232 and bug 52014 were resolved.

This problem with focus when tabbing was fixed and is currently working and I think it worked in rtm as well. Can this bug be closed now?

It worked nicely last time I tried it (except for the long delay sometimes in bringing up the window and filling out the defaults, during which tabs and clicks don't work right).

it looks like people thing this is working so I'm going to mark WORKSFORME.

OK, marking verified worksforme