Closed
Bug 81398
Opened 24 years ago
Closed 23 years ago
[tabbing] tab focus cycles through form elements in wrong order
Categories
(Core :: DOM: Core & HTML, defect)
Tracking
()
VERIFIED
FIXED
mozilla0.9.6
People
(Reporter: rh0209ms, Assigned: bryner)
References
(Blocks 1 open bug, )
Details
Attachments
(2 files, 1 obsolete file)
579 bytes,
text/html
|
Details | |
11.39 KB,
patch
|
bryner
:
review+
|
Details | Diff | Splinter Review |
Visit above URL, and then notice how pressing TAB moves the cursor to the
various form elements in wrong order.
Same with the "Contact Us" JavaScript-based form here:
http://www.unopiueuropa.de/coming_soon/index_ted.htm
It's not like that with Netscape Navigator 4.77 and neither Opera. TAB should
cycle through the elements from top to bottom, left to right.
Comment 1•24 years ago
|
||
Comment 2•24 years ago
|
||
The problem with the reduced test case is the the align="left" on the table. if
you remove that then the tabindex=0 gets the focus, but then it messes up again
after that.
Also note: My soon to be checked in docshell nav code doesn't change the
behavior of this.
Also, when the aligh="left" is there the GetNextTabbableContent returns nsnull
instead of the zero'th item.
Assignee: rods → saari
Status: UNCONFIRMED → NEW
Ever confirmed: true
Assignee | ||
Updated•23 years ago
|
Status: NEW → ASSIGNED
Target Milestone: --- → mozilla0.9.3
Updated•23 years ago
|
Target Milestone: mozilla0.9.3 → mozilla0.9.4
Assignee | ||
Updated•23 years ago
|
Summary: tab focus cycles through form elements in wrong order → [tabbing] tab focus cycles through form elements in wrong order
Assignee | ||
Comment 5•23 years ago
|
||
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
Assignee | ||
Comment 6•23 years ago
|
||
Ok, the problem here was that we weren't properly handling placeholder frames.
I've rewritten the frame traversal for tabbing to take into account placeholder
frames and give the real frame instead. In addition to this bug, this fixes
85217 and 88740.
Assignee | ||
Comment 7•23 years ago
|
||
Comment 8•23 years ago
|
||
okay, code looks good, r=saari with testing to death
Assignee | ||
Updated•23 years ago
|
Attachment #47578 -
Attachment is obsolete: true
Assignee | ||
Comment 9•23 years ago
|
||
Assignee | ||
Comment 10•23 years ago
|
||
The new patch has the same basic idea, just some logic cleanup and optimization.
Comment 11•23 years ago
|
||
r=saari again, looks good
Assignee | ||
Comment 12•23 years ago
|
||
Comment on attachment 48123 [details] [diff] [review]
patch
updating from saari's r=
Attachment #48123 -
Flags: review+
Comment 13•23 years ago
|
||
sr=hyatt
Assignee | ||
Comment 14•23 years ago
|
||
fix checked in.
Status: ASSIGNED → RESOLVED
Closed: 23 years ago
Resolution: --- → FIXED
Comment 15•23 years ago
|
||
The tab doesnt even go into the page, it tabs from url bar to the sidebar, and
back... When you click on one of the fields in the testcase and press tab it
tabs to the link and then to the url bar and you cant tab back to the page.
Reopening. This is on windows 98 so I'm changing platform to all. Increasing
severity to normal, because you cannot acess form fields with tab at all.
Severity: minor → normal
Status: RESOLVED → REOPENED
OS: Linux → All
Resolution: FIXED → ---
Target Milestone: mozilla0.9.5 → mozilla0.9.6
Assignee | ||
Comment 16•23 years ago
|
||
What build are you seeing this on?
Comment 17•23 years ago
|
||
2001-10-08-05-0.9.4 build on windows 98 for example
Assignee | ||
Comment 18•23 years ago
|
||
If you test on a trunk build, you should see that this is fixed. Please don't
reopen bugs because they aren't fixed in 0.9.4 builds if they were checked in
after 0.9.4 branched (which was on 9/4). If you'd like to nominate it for
checkin on the 0.9.4 branch, add the appropriate keywords. I'm going to go
ahead and remark this as fixed.
Thanks.
Status: REOPENED → RESOLVED
Closed: 23 years ago → 23 years ago
Resolution: --- → FIXED
Comment 19•23 years ago
|
||
bryner@netscape.com: The current behaviour is that tabindex 1 gets selected
first, then tabindex 2, only then tabindex 0 is selected...
This is the same behaviour as IE, but I would guess it should go to 0 before
going to one... is this a bug?
Assignee | ||
Comment 20•23 years ago
|
||
No, the HTML spec defines it to work this way.
Comment 21•23 years ago
|
||
Heh, read right over it :)
Verifying on windows 98 2002-01-07-03-trunk and linux RedHat
2002-01-04-08-trunk
Status: RESOLVED → VERIFIED
Updated•6 years ago
|
Component: HTML: Form Submission → DOM: Core & HTML
You need to log in
before you can comment on or make changes to this bug.
Description
•