|
|
Posted by VK on 04/22/07 12:51
On Apr 21, 2:04 am, Neo Geshel <got...@geshel.org> wrote:
> I am in the process of creating a template for a site. The site will be
> *true* XHTML 1.1
XHTML is gone and will never come back. Get some Prozac or some beer
or both and try to move further with your life.
:-) :-|
Note: Since 1999 I tried to get The Idea behind XHTML and I missed it
miserably - due to my narrow mental capabilities of course. OK, so
instead of hidden errors and possibly wrong resulting DOM Tree like in
HTML one will get "Page parsing error" message in XHTML. So kind of
"inevitable punishment" or so... Cool... I'm still missing the factor
preventing anyone to make valid HTML pages on the first place. If the
factor of "inevitable punishment" is so important, just make a program
sending a 1sec 110 V discharge to electrodes on each W3C Validator
error. Fix these electodes on your bo... sensitive part of your body -
and go ahead with the development: regularly validating your pages.
Functionally it is much more superior alternative to XHTML, really -
and fully cross-browser compliant.
"IE problem" is not simply that "IE doesn't support XHTML and Gecko
does". IE has very different HTML and XML models - in many aspects
superior to ones of other rivals. W3C and followers have to catch up
quickly now because all their time reserves were wasted for XHTML
experiments.
First of all, IE XML parser respects and loads external DTDs So all
these
<!DOCTYPE Extremely Utterly Strict XHTML> lines in XML parsing mode
being loaded and searched for extra entities. Gecko browsers are not
capable to use external DTD so they remain what they are intended to
be by W3C model: useless bogus strings at the top of the document to
silently disregard.
The second and maybe the most important difference is the namespace
mechanics. By Microsoft HTML has namespace and may have any amount of
extra namespaces. By W3C HTML doesn't have any namespaces, only XML
does. Unfortunately HTML 5 drafts by WHATWG still follow this W3C non-
sense despite no one of existing UA respects it - you can use
namespace'd DOM methods just fine on both Gecko and Opera. Now when
HTML5 is taken into a serious production this is the first thing to
fix.
Back to your original aim: if you feel that by using XHTML you are
"making the world better" or "defeating Micro$oft" then so shall be
it. People oftenly wasting their lifetime for even more bizarre
projects.
Technically you have to find a way then to forbid to IE to resolve
external entities. I believe XML has attributes and commands to
achieve this. comp.text.xml NG may be of a greater help.
Navigation:
[Reply to this message]
|