Closed
Bug 193157
Opened 22 years ago
Closed 21 years ago
<tab> navigation does not work as expected
Categories
(Core :: DOM: UI Events & Focus Handling, defect)
Tracking
()
RESOLVED
WORKSFORME
People
(Reporter: hme, Assigned: aaronlev)
References
()
Details
Attachments
(1 file)
79 bytes,
text/html
|
Details |
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.2.1) Gecko/20021130
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.2.1) Gecko/20021130
Context: In this form I've got two input-fields and a button aligned
horizontally. The tab-navigation between the fields doesn't work as expected.
This might be a javascript problem - I don't know. Here is the code concerning
the form and its surrounding table:
<table width="100%" border="0" cellspacing="0" cellpadding="0">
<form action="/bad" method="POST" name="dataentry">
<tr><td colspan="3"> </td></tr>
<tr>
<td width="33%"><font face="Verdana" size="2"
color="#845A9E"><b>brugernavn</b></font></td>
<td width="33%"><font face="Verdana" size="2"
color="#845A9E"><b>adgangskode</b></font></td>
<td width="33%"><img height=1 alt=""
src="/graphics/tiscali_dk/null.gif" width=1 border=0></td></tr>
<tr><td><input type="text" name="username" size="20"
maxlength="100"></td><td><input type="password" name="password" size="20"
maxlength="40"></td><td><a href="" OnClick="OnPhoenixLogin(); return false"
><img src="/graphics/tiscali_dk/b_entra.gif" border="0"></a></td></tr>
</form>
</table>
Reproducible: Always
Steps to Reproduce:
1. Go to http://webmail.tiscali.dk
2. Press <tab> twice
3. Press <enter>
Actual Results:
jumps from input 1 to input 2 to a link
(http://support.tiscali.dk/kontaktsupport.php) on the bottom of the page,
outside the current table and all.
Expected Results:
jump from input 1 to input 2 to the button and then submit the form
I submitted this bug first time about 2 years ago, but it persists. Maybe it's a
feature, then. :-)
![]() |
||
Comment 1•22 years ago
|
||
There is no button involved... there is an image inside an <a> tag. The <a> tag
has no href, so it's not a link. So why would we tab to it? (for that matter,
how is someone with JS disabled supposed to use it?)
Component: Browser-General → Keyboard: Navigation
Reporter | ||
Comment 2•22 years ago
|
||
If JS is disabled, you can still use the mouse. I guess that it's no argument
that it works on IE 5.5 (and earlier) and Netscape (4.6, 4.7)?
![]() |
||
Comment 3•22 years ago
|
||
> If JS is disabled, you can still use the mouse.
You're assuming that a mouse is being used to start with. This is a very bad
assumption. That said, if JS is disabled using the mouse will get you what
exactly? Why not just use an <input type="image"> if that's what you want?
In any case, over to the right component.
Assignee: asa → aaronl
QA Contact: asa → sairuh
![]() |
||
Comment 4•22 years ago
|
||
Confirmed on latest Windows nitely on XP.
Per comment #1, tho there's no href, there is an img that "submits" form data,
which is very common. Thus this is a real bug cuz the expected behavior works on
other browsers. There's no reason it can't be implemented in Mozilla.
![]() |
||
Comment 6•22 years ago
|
||
> there is an img that "submits" form data
No there is not. There is an image that executes some script on being clicked.
That script submits the form. This is very much an edge case. The _common_
thing is to have an <input type="image"> that submits the form, and those _are_
in the tab order in Mozilla.
Comment 7•21 years ago
|
||
I see no probblem using Firefox 0.9. I have found no duplicates of this bug and
am going to set it to status: WORKSFORME. If anymore info arises, I will change it
Status: UNCONFIRMED → RESOLVED
Closed: 21 years ago
Resolution: --- → WORKSFORME
Assignee | ||
Comment 8•21 years ago
|
||
In Firefox 1.1 or some future build you should be able to use tabindex on any
element (bug 171366). You'll also need an onkeypress to detect the Enter key.
Again, this is work only going on in the trunk.
Updated•6 years ago
|
Component: Keyboard: Navigation → User events and focus handling
You need to log in
before you can comment on or make changes to this bug.
Description
•