Tigdh Glesain wrote:

> http://www.webdevout.net/articles/beware-of-xhtml#what_is_xhtml

Since the quality of the mark-up is crucial for CSS to work, I have no
problems discussing the issue here on css-d.
However: the issue is about technical conformance and practical use
(serving) of XHTML, so opinions about what's right and/or wrong beyond
that is off-topic, IMO.

> If I am writing good XHTML markup and 'matching' my css to a standard
>  on par with my markup, am I being led down a path that may become a
>  repeat of the "forked-code wars" of the late 1990s, et al?

That article is well worth paying attention to, as too many pages/sites
with an XHTML doctype on the web today, are *not* XHTML at all. They are
flawed HTML, which equals "pure garbage served under false name".
There's not all that many useful details in the article itself, so you
will have to look for facts elsewhere - preferably at the W3C site.


If you are writing _perfect_ XHTML 1.0, and also assure that your
markup/CSS/scripts/whatever works as intended when served properly (as
'application/xhtml+xml') to XHTML/XML aware browsers, then you have
nothing to worry about - regardless of how it is served.

However, one flaw in your XHTML mark-up, and it may break when served
properly. This is where it easily gets problematic, as it is hard to
enforce and guarantee _perfection_ for a site into the future.

> Am I worrying unnecessarily?  Do any of have any 'jeez' to go with my
>  'whine'? (O:

You have good reasons to worry if your work either isn't up to _perfect_
XHTML standard from the very start, or someone else may lower its
quality in the future. There is *no* [error recovery] for properly
served XHTML.

Browsers _are_ quite "forgiving" for minor - and also some major flaws -
in HTML, and the same goes for XHTML served as 'html/text'. This makes
many think their "XHTML decorated" pages are "good enough", since
browsers render them fine when they are served as 'html/text' and the
validator says it looks ok. Not necessarily so, as one may learn the
hard way if/when XHTML is served properly as 'application/xhtml+xml'.


More on the subject:
<http://www.gunlaug.no/contents/wd_1_06_03.html>
...and mind the perfect and intentionally flawed *quick test* copies
linked in in that page, which proves the points about quality and
perfection. Use a proper browser, as IE doesn't support anything served
as 'application/xhtml+xml'.

regards
        Georg
-- 
http://www.gunlaug.no
______________________________________________________________________
css-discuss [EMAIL PROTECTED]
http://www.css-discuss.org/mailman/listinfo/css-d
IE7 information -- http://css-discuss.incutio.com/?page=IE7
List wiki/FAQ -- http://css-discuss.incutio.com/
Supported by evolt.org -- http://www.evolt.org/help_support_evolt/

Reply via email to