As long as you're serving XHTML as text/html it isn't XML anyway. It's
just HTML with some weird slashes where they don't belong. Any
browser will use its tag soup parser.
Mime type matters, Doctype not.
http://annevankesteren.nl/2004/07/mime
And that's why you can safely use HTML if you add el
Yup. Nothing to be done about it.
Karl Rudd
On Sun, Feb 24, 2008 at 3:18 PM, timothytoe <[EMAIL PROTECTED]> wrote:
>
> OK. Since I'm creating so much of the web site on the fly, there's
> really no way of knowing whether I'm valid or not, is there? I mean
> it's pretty easy to make my trivial
OK. Since I'm creating so much of the web site on the fly, there's
really no way of knowing whether I'm valid or not, is there? I mean
it's pretty easy to make my trivial, skeletal html (or php) file
valid--there's hardly anything in it!
I tried to go through all the paths and validate. I guess I
It's not a problem.
I assume you're viewing the DOM tree via Firebug (or something
similar)? If so then what you're seeing is a representation of the
tree that Firebug is generating.
The concept of XHTML vs HTML (vs XML) is pretty much gone after the
(X)HTML is parsed and turned into the DOM tre
Try
http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd";>
And XHTML mandates the use of quotation marks not apostrophe's which is
probly why its getting converted
~ Big Dog
timothytoe wrote:
> Not sure this is 100% jQuery's problem.
>
> I do this:
>
> $("#logo").html("");
>
> But what l
5 matches
Mail list logo
