Closed Bug 83566 Opened 23 years ago Closed 23 years ago

[tabbing] Dead spots should not be included in tab order cycle.

Categories

(Core :: DOM: UI Events & Focus Handling, defect)

x86
Other
defect
Not set
normal

Tracking

()

VERIFIED FIXED
mozilla0.9.6

People

(Reporter: loeb, Assigned: bryner)

References

(Blocks 1 open bug)

Details

Whether they are hidden fields, or entire windows being highlighted, or other,
they should not appear in the tabbing cycle. Tabbing cycle should be limited to
links, the URL bar, form controls, and frames/content window.

A lot of times the focus gets lost. To duplicate, click in the URL bar, press
tab, and where are you? Not on the first link in the content area where you
should be.
Blocks: focusnav
FYI, i believe after the first tab we are focus on the top level content
window/frame/thingy. Using MSAA event viewer you can see where the focus goes
and track it.
Status: UNCONFIRMED → NEW
Ever confirmed: true
see also my bug for the "dead spot" when cycling through frames: bug 82656.
No longer blocks: focusnav
bryner taking dead spot bugs
Assignee: aaronl → bryner
No longer depends on: focusnav
Blocks: focusnav
Ok, we have to give the page document focus at _some_ point... perhaps we could
show it visually so it doesn't appear to be lost.  We also need to suppress
giving the document focus for chrome documents (I think).
Status: NEW → ASSIGNED
Target Milestone: --- → mozilla0.9.3
Target Milestone: mozilla0.9.3 → mozilla0.9.4
Summary: Dead spots should not be included in tab order cycle. → [tabbing] Dead spots should not be included in tab order cycle.
*** Bug 88979 has been marked as a duplicate of this bug. ***
moving these out to 0.9.5 since it doesn't look like I will have time for 0.9.4.
Target Milestone: mozilla0.9.4 → mozilla0.9.5
Mass-moving lower-priority 0.9.5 bugs off to 0.9.6 to make way for remaining
0.9.4/eMojo bugs, and MachV planning, performance and feature work. If you
disagree with any of these targets, please let me know.
Target Milestone: mozilla0.9.5 → mozilla0.9.6
No known remaining cases left, if you find one, reopen with a specific test case
Status: ASSIGNED → RESOLVED
Closed: 23 years ago
Resolution: --- → FIXED
see aaronl's 2001-11-05 09:33 comments in bug 108291 --should this be reopened,
or marked wontfix?
okay, vrfy'ing due to clarification from aaronl in bug 108291.
Status: RESOLVED → VERIFIED
Component: Keyboard: Navigation → User events and focus handling
You need to log in before you can comment on or make changes to this bug.