Quote:
Originally Posted by pietvo
I see. In that case it makes many more (syntactic) changes to let it look more like HTML instead of XHTML.
|
Firefox will do a few tidying operations such as adding an http-equiv entry if the input doesn't have one and converting some empty tags like <p/> to <p></p>. But it doesn't modify fragment identifiers, which could trip up some user agents. Firefox doesn't interpret <br></br> correctly and therefore messes up the output, but that's a fairly unlikely construct (though valid in xml).