Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

Mobile Firefox puts a (possibly unstyleable?) blue box around <a>

  • 3 odgovori
  • 2 ima ovaj problem
  • 6 views
  • Posljednji odgovor poslao AaronMT

more options

Consider the following reduced example:

<html>
    <head>
        <style type="text/css">
            a, a:focus, a:active, a:hover {
                outline: none;
            }
        </style>
    </head>
    <body>
        <a href="#foo">Test</a>
    </body>
</html>

Clicking the Test anchor creates a persistent blue box around Test text:

http://postimage.org/image/pvofegsiz/

It's not clear whether this border is styleable, or how to get rid of it.

Consider the following reduced example:<br /> <br /> <pre><nowiki><html> <head> <style type="text/css"> a, a:focus, a:active, a:hover { outline: none; } </style> </head> <body> <a href="#foo">Test</a> </body> </html></nowiki></pre> Clicking the Test anchor creates a persistent blue box around Test text: http://postimage.org/image/pvofegsiz/ It's not clear whether this border is styleable, or how to get rid of it.

Izmjenjeno od strane cor-el

All Replies (3)

more options

This forum does not handle raw HTML well. Try editing your post and replacing your left angle brackets (<) with the equivalent HTML entity (&lt;).

On an image in an anchor tag, you can set border=0 to remove the box around the image. Does that have any effect in your case?

Edit: If you mean the focus outline, there may be other solutions for that. You might look up the CSS outline property.

Izmjenjeno od strane jscher2000 - Support Volunteer

more options

The anchor just contains text, no image, so setting the border property does not resolve this.

Setting outline:none also does not resolve this, as shown in the (now updated) example.

Any insight would be appreciated. Thanks.

more options

Hey Jbear4,

It is indeed a bug. We have it on file on bug 719276. Feel free to follow along in that bug report.