Separate names with a comma.
Discussion in 'Web Design and Development' started by iGav, May 3, 2007.
I think that summarizes everything. It complains that CSS Zen Garden and Mezzoblue don't show when parsed as XML, but whatever. As long as the sites work for me, I'm happy.
As a designer, I just want my sites to work. And although I understand the philosophy of the people making standards, I don't necessarily need to abide by them.
It shouldn't be "beware of XHTML" but rather "XHTML doesn't do what it in principle should do" that is, it still too much like HTML and not enough XML.
I haven't had any problems sticking with xhtml-transitional yet, and haven't had a need for xhtml-strict, yet.
Whether we're talking about XHTML or something else, it's still very important for web content producers to continue to push browser developers to support progressive web standards.
I'm sure if we look we could find criticisms from the past along the lines of "HTML 3.0 is bad; HTML 2.0 is good enough."
Articles like that don't mean XHTML is bad. It's just to inform you that HTML is still a standard and XHTML can't get parsed as XML in most browsers which is one of the main benefits of using it in the first place. Personally, I think XHTML strict is good practice from a coding/semantics perspective regardless of whether it's being parsed as html or not. I like all the rules that go along with XHTML and I think html lets people become very sloppy.
I agree. Using XHTML strict certainly makes you keep your head above water. HTML has always been abused by "designers" and a lot of WYSIWYG apps. By using XHTML (more so strict) I am sticking to standards and keeping lean code which will have more longevity than sloppy HTML that usually needs "amending" whenever a new browser version gets released.
Long story short: Nobody is feeling like creating an XML parser in their web browser that works correctly, as well as web designers not doing their homework on how to use XHTML code.
I tried to start polishing up my web application to validate to XHTML, and it actually ended up breaking mine.
I had a text box, and suddenly half my code decided to move into it and live there :-\
Had to grab a backup, got lost in the forest of line numbers and have to give up.
I don't understand the need for so many standards, if they all do the same damn job.
HTML isn't very good with assistive technologies such as screen readers, as well as having the benefits of the XML format.
Some do it better than others and standards help with that. When I debug XHTML/CSS, the first thing I do is make it validate. It usually helps identifying the problem or deducing the problem.