Closed Bug 115254 Opened 23 years ago Closed 23 years ago

Using the tab key doesn't move to the next field on a web page properly

Categories

(SeaMonkey :: General, defect)

x86
Windows 98
defect
Not set
major

Tracking

(Not tracked)

VERIFIED DUPLICATE of bug 114976

People

(Reporter: robb, Assigned: asa)

References

()

Details

From Bugzilla Helper: User-Agent: Mozilla/5.0 (Windows; U; Win98; en-US; rv:0.9.6+) Gecko/20011213 BuildID: 2001121313 When filling out forms and such on web pages, clicking the Tab key should move the cursor or focus to the next field/button/element on the page. Instead, what happens is that clicking on the tab key will focus first the address line, then any buttons in open sidepanels, then focus on each element on a webpage until getting to the current field, which is when (finally) it will move to the following field. Reproducible: Always Steps to Reproduce: 1. (Using Google as an example.) Enter in a search term in the text box. 2. Hit the Tab key. Actual Results: When pressing the tab key on step 2, the URL is instead focused in the Address window, instead of the 'Google Search' button. Expected Results: The Google Search button should have been focused as the next field/button/link. This seems to be a new bug, as the tab key moved the focus to the next field/button/link on a web page in the 20011210 build.
As an additional aside: If, after the first 'mis-focus', you click on the field you're using (such as the search text box on the google page) and then click the tab key, it moves to the next element on the web page properly. It's more bizzare, because normally you need to click on the field in the first place to enter text. That requires taking hands off the keyboard to use the mouse, though, which definitely slows down productivity.
Dupe of 114976
Hrm. Didn't find the original when I did a search. *** This bug has been marked as a duplicate of 114976 ***
Status: UNCONFIRMED → RESOLVED
Closed: 23 years ago
Resolution: --- → DUPLICATE
vrfy dupe
Status: RESOLVED → VERIFIED
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.