Skip to main content

Disable grey border on anchor (<a>) elements on focus



I am trying to make the ugly grey border that appears around anchor tags go away. The CSS property " outline:none; " works for Firefox, but how can I do it in IE. Preferably using CSS expressions or jquery. I'm not worried about accessibility BTW.





Based on your suggestions I found these to be the best solutions...





The jquery(for IE browsers):







$('a').focus(function(){

$(this).blur();

});







Another jquery option(for IE browsers only):







$('a').focus(function(){

$(this).attr("hideFocus", "hidefocus");

});







The CSS(For all other browsers that force an outline):







a{

outline: none;

}







Note: Some browsers such as Google Chrome don't force an outline on focus.



Source: Tips4all

Comments

  1. Unfortunately I think hideFocus is your best answer as blur isn't always appropriate:

    <a href="..." hidefocus="hidefocus">...</a>


    http://msdn.microsoft.com/en-us/library/ms533783(VS.85).aspx

    ReplyDelete
  2. It sounds like you're talking about the dotted border that appears when you tab through links. You have the correct solution for Firefox (outline: none in the CSS). The best solution I've used for IE is to add an onfocus listener that removes focus:

    <a href="" onfocus="this.hideFocus=true;">link</a>


    Take a look at this site for an example of how you might do it globally: http://codylindley.com/Javascript/223/hiding-the-browsers-focus-borders-should-i-shouldnt-i

    ReplyDelete
  3. For IE, you can use Javascript like this:

    <a href="..." onfocus="this.blur();">Click Here</a>


    Read more:
    http://www.htmlgoodies.com/beyond/javascript/article.php/3471171

    For Firefox and Safari, outline:none works.

    Read more:
    http://css-tricks.com/removing-the-dotted-outline/

    ReplyDelete
  4. Unless I'm missing which dotted border is being discussed, outline:none works in Internet Explorer 8 (at least, for me). Rather all of a sudden some hyperlinks were rendering with a dotted border (the only attribute I remember changing is display:inline on an h2 element that contained a link, afterwards the dotted border appeared). So I threw in a { outline:none; } in my global stylesheet and poof, no more border in IE8!

    ReplyDelete
  5. Does this not work?

    a
    {
    border: 0;
    }

    ReplyDelete
  6. a {outline:noneIE 8} css seems to work well on Firefox, Chrome and IE 8.

    ReplyDelete

Post a Comment

Popular posts from this blog

[韓日関係] 首相含む大幅な内閣改造の可能性…早ければ来月10日ごろ=韓国

div not scrolling properly with slimScroll plugin

I am using the slimScroll plugin for jQuery by Piotr Rochala Which is a great plugin for nice scrollbars on most browsers but I am stuck because I am using it for a chat box and whenever the user appends new text to the boxit does scroll using the .scrollTop() method however the plugin's scrollbar doesnt scroll with it and when the user wants to look though the chat history it will start scrolling from near the top. I have made a quick demo of my situation http://jsfiddle.net/DY9CT/2/ Does anyone know how to solve this problem?

Why does this javascript based printing cause Safari to refresh the page?

The page I am working on has a javascript function executed to print parts of the page. For some reason, printing in Safari, causes the window to somehow update. I say somehow, because it does not really refresh as in reload the page, but rather it starts the "rendering" of the page from start, i.e. scroll to top, flash animations start from 0, and so forth. The effect is reproduced by this fiddle: http://jsfiddle.net/fYmnB/ Clicking the print button and finishing or cancelling a print in Safari causes the screen to "go white" for a sec, which in my real website manifests itself as something "like" a reload. While running print button with, let's say, Firefox, just opens and closes the print dialogue without affecting the fiddle page in any way. Is there something with my way of calling the browsers print method that causes this, or how can it be explained - and preferably, avoided? P.S.: On my real site the same occurs with Chrome. In the ex