Closed Bug 338035 Opened 19 years ago Closed 12 years ago

No visual focus for <a> w/o href when it gets focus (still focusable if tabindex attribute present)

Categories

(Core :: Layout, defect)

x86
Windows XP
defect
Not set
normal

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: mdfft, Assigned: MatsPalmgren_bugz)

References

(Blocks 1 open bug)

Details

(Keywords: access)

Attachments

(1 file)

Env: Bon Echo 20060515 nightly build Description: The "tabindex" attribute will cause a tab stop to be inserted into a web page. The anchor tag <a> supports the tabindex attribute. There should be a visual focus indicator around the text between the anchor tag <a> and the end anchor tag </a> to let a keyboard user know where current keyboard focus is. Steps to Recreate: For example, the following html will add a tab stop to a text string using the anchor tag: <a tabindex="0" name="anchor2"> This text should show dotted line around it when you tab to this tab stop. </a> (Internet Explorer displays the visual focus dotted line around the text okay.)
Attachment #222072 - Attachment mime type: text/plain → text/html
Blocks: focusnav
Target Milestone: --- → Firefox 3 alpha1
Confirmed. I have discovered that this is specific to the <a> element. If you change <a tabindex="0"> to <span tabindex="0">, Firefox shows the focus rectangle as expected.
Assignee: nobody → aaronleventhal
Component: Disability Access → Disability Access APIs
Product: Firefox → Core
QA Contact: disability.access → accessibility-apis
Target Milestone: Firefox 3 alpha1 → ---
Blocks: fox3key
Summary: No visual focus for text within anchor tag with tabindex=0 → No visual focus for <a> w/o href when it gets focus (still focusable if tabindex attribute present)
I suspect that this rule in ua.css doesn't work when there's no href. Probably part of what -moz-any-link means. *|*:-moz-any-link:focus { outline: 1px dotted invert; } The other focus rules are in html.css, and don't list |a|
Assignee: aaronleventhal → oliver_yeoh
I guess this is related to bug 267119, right?
I'm not sure about right component, it sounds like styling issue of HTML.
Assignee: oliver_yeoh → nobody
Component: Disability Access APIs → Layout
QA Contact: accessibility-apis → layout
Assignee: nobody → matspal
WFM, Nightly 23.0a1 (2013-04-19) Linux64.
Status: NEW → RESOLVED
Closed: 12 years ago
Flags: in-testsuite?
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: