It's not a bug in Firefox, you're getting an extra <a></a>
in there in the first place...I'd disable all your plugins and try again, something specific on your install is interfering here.
I assume you're viewing this with Firebug, does the exact example you gave above (with nothing else in the page) do the same thing? You can try a demo here: http://jsfiddle.net/Wcjk9/
Update:
Your example does indeed show some weird behavior in Firefox, however it's "allowed" to do this. Since you have invalid HTML, the browser can and indeed is giving some funky behavior here. The parser/scripting engine in the browser is free to assume you have valid HTML, like unique IDs for example. If you have invalid HTML, well...it can't be held responsible. I have to include this quote:
On two occasions I have been asked, 'Pray, Mr. Babbage, if you put into the machine wrong figures, will the right answers come out?' I am not able rightly to apprehend the kind of confusion of ideas that could provoke such a question.
Ignoring the errors that jsbin adds, you can see the problem here (the first validation error). You are not allowed to have a block element inside an anchor. You can have an inline element, if you replace the <p>
in your example with a <span>
you'll have valid HTML...and this weird behavior goes away :)