Closed
Bug 315335
Opened 19 years ago
Closed 19 years ago
Clicking image with link shows border focus as dotted rectangle
Categories
(Firefox :: General, defect)
Tracking
()
RESOLVED
INVALID
People
(Reporter: it, Unassigned)
References
()
Details
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8) Gecko/20051025 Firefox/1.5
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8) Gecko/20051025 Firefox/1.5
When I click on an image link, a dotted rectangle appears around the image. This behaviour did not occur in older Mozilla versions, and does not appear in MS IE.
Reproducible: Always
Steps to Reproduce:
1. Goto http://www.altavista.com/
2. Click and hold on the AltaVisa logo.
3. Keep mouse button held down, and move cursor off logo
4. A dotted "focus" box appears around the image
Expected Results:
The dotted rectangle should not appear
CSS a:focus border:none has no effect, and the dotted rectangle does not appear to be removable.
Comment 1•19 years ago
|
||
> When I click on an image link, a dotted rectangle appears around the image.
That's good. Mozilla needs to show where focus is in order to be accessible.
> This behaviour did not occur in older Mozilla versions
Due to a bug bug (probably bug 65917).
> and does not appear in MS IE.
For me, it does appear in IE. I'm testing with a beta of IE7 on http://www.altavista.com/.
> CSS a:focus border:none has no effect, and the dotted rectangle does not
> appear to be removable.
Try turning off outlines (not borders) on the image child of a focused link (not the link itself). But why would you want to hide focus?
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → INVALID
Reporter | ||
Comment 2•19 years ago
|
||
It seemed like a bug because behaviour had changed from earlier versions, but you're right, the bug was probably in the earlier versions.
And again you are correct, the CSS required to remove the focus is:
a:active, a:focus {
outline:none;
}
I am sure this will work on all elements, including form submit as well.
You need to log in
before you can comment on or make changes to this bug.
Description
•