Tom Baxter wrote:
> "Donald Anadell" wrote:
>> "Tom Baxter" <firstname.lastname@example.org> wrote in message
>> Try changing the closing tag for the <Break> to look like this "<br />",
>> instead of "</br>".
> Yes, of course I could do that but that's not the point. The point I am
> making is that <br></br> should equivalent to <br/> and that while IE 8
> handle <br/> as one line break it treats <br></br> as two.
> I was not asking how to get one line break.
Only if you expect the web browser to handle *badly* coded HTML. Some
do and why they promote badly coded web sites. Don't rely in the slop
in one web browser to exist in another. There is no </BR> tag. BR
doesn't have a span or content over which it applies its effect. It is
a singleton tag. That means it doesn't get a matching closing tag. It
must be in the self-closing form, and those have the slash at the *end*
of the tag attributes, not at the start (because you aren't closing a
prior instance of that same tag; that is, there is no content to the
singleton tag). The self-closing singleton tags are:
(The delimiting space character is no longer required.)
However, you aren't using XHTML, anyway. Self-closing tags aren't valid
(and will be ignored for their implied closure) when rendering the
document as HTML. So <br/> is just <br> in HTML (the slash gets ignored
as an invalid attribute. What you have is HTML with XHTML DOCTYPE.
DOCTYPE does not determine how document is interpreted. MIME type does.
Read the section titled "What determines if my document is HTML or
XHTML?" part of which is:
In fact, the vast majority of supposedly XHTML documents on the
internet are served as text/html. Which means they are not XHTML at
all, but actually invalid HTML that¢s getting by on the error handling
of HTML parsers. All those 'Valid XHTML 1.0' links on the web are
really saying 'Invalid HTML 4.01'!
This article also mentions:
Validate your content as HTML, not as XHTML. One handy way is using a
validation service, such as the W3C Validator. (But beware, the
validator looks at your doctype instead of the MIME type, unlike
I don't see you declaring the MIME type as application/xhtml+xml or
text/xml. The above article was written in 2006. IE7 didn't handle
XHTML (and IE8 won't in its IE7 quirks mode).
(this discusses lack of XHTML support in IE7).
From Googling around, it appears IE8 still does not support XHTML. See
Internet Explorer, using the Trident layout engine ...
does not support XHTML, though it can render XHTML documents authored
with HTML compatibility principles and served with a text/html
Only the text/html MIME type is supported contrary to all other modern
web browsers that support the xml+xhtml or xml media types. That means
it will render those pages as HTML. So your </br> tag is getting
interpreted as <br>. Microsoft didn't want to hack their Trident engine
to add XHTML support and end up with a bunch more quirks, so they're
writing it from scratch. Anyone's guess now if XHTML will be supported
So it's not a bug. It's a continued lack of XHTML support (assuming you
had actually specified an XML/XHTML media type in your document
declaration, which you didn't).