Scroll up or down a screen full Page Up or Page Down Go to top of page Ctrl+Home (Win.4.X) Home (Mac 4.X) Go to bottom of page Ctrl+End (Win.4.X) End (Mac 4.X) The Tab key will cycle through controls and items generally from top to bottom left to right. To reverse this order use Shift+Tab. Once the cycling finishes with those defined in one area the tab order will take it to the next area/frame. Browser the Tab order is 1. URL 2. Web Page Items ...(however many there are) 3. Open sidebar and the items in the open panel of the sidebar 4. Back to URL In Email the Tab will cycle through 1. Folders pane 2. Subject pane 3. Message pane 4. Open sidebar and the items in the open panel of the sidebar 5. Folders pane Shift+Tab will operate as Tab but in the reverse order.

This is the Keyboard Navigation functionality that are Must Haves for all parts of Netscape6. Additional Keyboard Navigation functionality will be addressed in another bug. Keyboard Navigation functionality that differs in functionality depending on which app you are in have their own Must Have and Additional buggs Codeing comentary is welcome here. Other comentary please see the tracking bug.

I think Ben was experimenting with tab order. Also, I can help out with this as needed.

since this mentions several issues, is this going to be a meta bug? (for example, there's tabbing bug 20159, which could be marked as a blocker for this one.) if this isn't a meta bug, i'd prefer keeping one issue per report. thx!

This is only one of a series of bugs. there will be at least partial implimentation of tabbing for NS6 release and a more complete implimentation later. This bug is only for that partial implimentation. I will be filing the companion bug tommarrow which will complete the tabbing feature but will be inplimented at a later date. This is priomarly for tracking completion of NSbeta3 P1 issues.

Just to be clear tabbing in the browser cycles through all elements, Links, Form Controls and Buttons. Not just links.

nsbeta3

This bug report contains too many subjects. This one is too broad. For example: Scroll up or down a screen full. What area are you talking about? Browser web page? Composer? Mail compose? Mail thread pane? Mail folder pane? IM buddy list? IM compose window? Bookmarks window? All of these items belong to various owners. I know that for mail, all the items you covered here are filed under separate bug reports. Lake, I'd suggest that you work with each QA team to see if there are existing bugs filed, and if not, file one bug per component area. Also, bug http://bugzilla.mozilla.org/show_bug.cgi?id=20159 about tabbing between links on a web page that Sarah references is already marked nsbeta3-. This bug, as it stands, probably won't be able to be fixed all by one person. (Pls correct me if I'm wrong, mcafee.)

This is a meta bug and we never give plusses to meta bugs. If you want to get bugs approved for nsbeta3 or rtm, please file separate bugs on the most serious items. Marking nsbeta3-

Closing this, since this isn't useful, and isn't even much of a meta bug (meta bugs usually depend on a list of bugs). This also probably belongs in bugscape (who is the "we"? Netscape?)

mass verification of Invalid bugs: to find all bugspam pertaining to this, set your search string to "MagaritaLuisaChascarilloAvoidsInvalidBugs". if you think this particular bug is *still* an open issue, please make sure of the following before reopening: a. where relevant, do check that it's actually still a problem with ***recent trunk builds*** on the all appropriate platform[s] b. provide clear, compelling reasons why this bug should be considered a valid one.