Closed Bug 170833 Opened 22 years ago Closed 22 years ago

TABINDEX not functional on Anchor or Button elements

Categories

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

PowerPC
macOS
defect
Not set
major

Tracking

()

VERIFIED INVALID

People

(Reporter: chrispetersen, Assigned: aaronlev)

References

Details

(Keywords: regression)

Build: 2002-09-25-11
Platform: OS X 10.2
Expected Results: Focus should be placed on each element (during tabbing)
What I got: When tabbing, a focus ring isn't appearing on anchor or button elements

Steps to reproduce:

1) Go to either test case

http://mozilla.org/quality/browser/standards/html/a_tabindex.html

http://mozilla.org/quality/browser/standards/html/button_tabindex.html

2) Read testcase description text and place focus on element specified

3) Press the tab key to move focus to the next element (in tab index)

4) Focus ring doesn't appear on the next element.
Priority: -- → P2
WFM in build 2002091014 PC/Win98.
Removed priority.  Only bug assignees should be setting/changing priority.
->keyboard nav
Component: Layout → Keyboard Navigation
Priority: P2 → --
Reassigning to owner of component.
Assignee: attinasi → aaronl
QA Contact: petersen → sairuh
This was working on the OS X Sept 17th trunk and doesn't seem to work on todays
build. Haven't researched when this regressed yet.
chris, if you're able to find out when this regressed, that'd be great --thanks!
Keywords: regression
Blocks: focusnav, atfmeta
Looks like the regression occurred on the 2002-09-19-03 Mozilla OS X build. I
have a 2002-09-18-03 Mozilla OS X build were tabindex is functioning using these
two test cases.
The mozilla builds referenced are trunk builds not branch.
just realized that what you're seeing might be intended behavior. default
tabbing changed recently (see bug 140612), so that on mac the tab key moves only
btwn textfields in a page.

while i understand this is frustrating, methinks this is an invalid bug. see bug
169045 which requests having an rfe for this behavior.
No longer blocks: focusnav, atfmeta
Also note that it's a pref, so you can set the behavior to be whatever you want.

// Tab focus model bit field:
// 1 focuses text controls, 2 focuses other form elements, 4 adds links.
// Most users will want 1, 3, or 7.
user_pref("accessibility.tabfocus", 7);
specific mozilla pref ui bug is bug 170871.
*** Bug 183326 has been marked as a duplicate of this bug. ***
*** Bug 183500 has been marked as a duplicate of this bug. ***
This also applies to Mac OS 9.1. Pressing tab no longer moves to the push
buttons on a form. This was working in Mozilla 1.1.
Okay, so I read bug 140612 (see comment 7) and find out that this "bug" is
really a fix for what some thought was broken tabbing behaviour. I didn't think
it was broken in 1.1. I visit one web site frequently where there are pages with
just a multi-line text entry field and a submit button. It was real nice to
enter what I wanted to say and press tab and enter. Now I have to take the extra
time to grab the mouse and click the submit button. Not everything can be done
easier and quicker with the mouse.

There seemed to be some discussion on having a UI preference to control the
behavior of tabbing. Personally, I would have implemented both changes in 1.2
rather than doing one, confusing users and then finally adding the preference in
the next version.
*** Bug 184685 has been marked as a duplicate of this bug. ***
*** Bug 186771 has been marked as a duplicate of this bug. ***
*** Bug 188129 has been marked as a duplicate of this bug. ***
Flags: blocking1.3b?
okay, since this sounds like it's due to the default tabbing behavior for mac,
i'm going to mark this as invalid. see bug 169489, where there's a patch to
[also] expose the tabbing nav pref.
Status: NEW → RESOLVED
Closed: 22 years ago
Keywords: nsbeta1
Resolution: --- → INVALID
Flags: blocking1.3b? → blocking1.3b-
v inv
Status: RESOLVED → VERIFIED
*** Bug 190509 has been marked as a duplicate of this bug. ***
*** Bug 233526 has been marked as a duplicate of this bug. ***
*** Bug 242299 has been marked as a duplicate of this bug. ***
*** Bug 246066 has been marked as a duplicate of this bug. ***
*** Bug 246745 has been marked as a duplicate of this bug. ***
*** Bug 293309 has been marked as a duplicate of this bug. ***
Component: Keyboard: Navigation → User events and focus handling
You need to log in before you can comment on or make changes to this bug.