Do you have a question? Post it now! No Registration Necessary. Now with pictures!
- Posted on
Steve Pugh wrote:
"No big deal that this code doesn't work on any of existing/ever
existed browsers and there are doubts that it ever will in any near
future. It is still fine - because it is theoretically correct."
Sometimes ciwas and siwah just nock me out: I feel like I got crazy -
or everyone around me did. :-)
It might help to accomodate if ciwah would be piwah:
But as I see "authoring" instead of "abstractions" then could we be a
tiiiny bit more reality connected?
Browsers supporting XHTML, receiving this mark-up as part of an XHTML
document (so served as an XHTML document), do not get this wrong.
Haven't you learnt yet that your pontificating about the generality of
web browsers suffers significantly form you lack of familiarity with web
browsers and your lack of understanding of web technologies? Existing
browsers do include Mozilla and Opera 8+.
It is you. When you find yourself in a minority of one the odds are good
that it is you who is wrong, and when you find yourself in a minority of
one in a technical newsgroup it is virtually a certainty.
Toby Inkster wrote:
Assuming "XHTML as XML, for only browsers that understand it" it's OK.
For anything else, including "XHTML as Appendix C" or "XHTML as tag
soup" OR "XHTML to anything at all that isn't playing the entire XML
game all the way" then it fails badly (IE6 will hide your whole
So as a general working practice for anything vaguley near "the web",
You need to preserve the separate start and end tag, no matter what.
This is one reason why it's awkward to produce viable XHTML from XSLT.
You have to stick some whitespace in there (to force the tags separate)
and the slightest sloppy coding in a default XML/XSLT mindset will
break your site
(Yes, I've done it on a live site and had an outage for a whole
:) Ok VK, point taken.
It's not my delusion/illusion actually, hence the thread. I have a user
complaining that our search robot is getting the contents of his page
wrong. He must think the page is working as he intends. I told him not,
but I would consult the wise and friendly experts. There is no other
source for his script. It's a whole gaggle of browser sniffing code
other things. He must be quite frustrated as to why it doesn't work :)