Why using anchors as buttons sucks

Re:Why using anchors as buttons sucks by talmand on Sunday February 05, 2012 @09:34AM (#3554108)

For a moment there I was trying really hard to understand what he was complaining about. His post made very little sense to me as it was written. I guess because I haven't even come close to experiencing his "problem".

Especially since I looked over the pull request he mentions and the explanation as to why href="#" is used is right there in front of his face.

Plus, what's with all the hate for href="#"? Are some people so anal about their code they can't leave one simple little thing in place that makes life easier for them?

[ Parent | on HN ]

Re:Why using anchors as buttons sucks by tkazec on Tuesday February 07, 2012 @03:32PM (#3563526)

>what's with all the hate for href="#"? Um, there was a section of my post explaining everything wrong with it, which was also further discussed in the G+ comments.

Of course I understand why keyboard accessibility (a benefit of href="#") is a good thing, that was a main point in the post: There's no solution for adding "buttons" (in the functionality sense) that look like standard links without major drawbacks, like a lack of keyboard control.

[ Parent | on HN ]