Rimantas Liubertas wrote: [...] > Once again > using XML brings nothing to the table if you use text/html.
Absolutely untrue. If nothing else, it brings the use of XML tools to test out your markup. And while people like Hickson don't seem to understand the importance of that, the fact is that it makes automated testing of your output *much* easier (rspec_hpricot_matchers, anyone?). And automated testing is exactly what we should be doing all the time. [...] > Well, even if names of Anne van Kesteren (Opera), Ian Hickson(Google, > author > and maintainer of Acid2 and Acid3 tests, editor of HTML5 spec), > Lachlan Hunt (Opera), Roger Johansson (prominent web standards advocate) > are not credible enough, you can always try for yourself and see. I don't care about names; I care about quality of reasoning. And while I'm sure most (not all) of the facts cited are accurate, the quality of reasoning in those articles is extremely low (see the comments to van Kesteren's article for some nice hole-poking). I do plan to set up some tests of my own. > I've done that five years ago: http://rimantas.com/bits/xhtml-test.php What's the point of citing 5-year-old tests? Software -- and standards -- can change greatly over periods that long. > > It is trivial to test if DOCTYPE affects if page is processed with HTML > or > XHTML parser (it doesn't) or is it only influenced by MIME type (it is). I can believe that (although I got it wrong at first). That is not a fact I am disputing, although I really am not sure why browsers are written this way. > Also it is not difficult to see that in XHTML mode CSS may be > interpreted > differently, I admit that I am having trouble seeing how the differences in CSS interpretation would be of any practical significance. > Javascript is affected (just try to add line if (x<y) in > your > Javascript, do not escape it with CDATA and serve with > application/xhtml+xml. > You will see what I am talking about. Or try to wrap your JS code with > <!-- //--> > and see if it runs at all). If you put inline JavaScript in your HTML, you deserve any problems you get. :) It's a stupid thing to do. > > Regards, > Rimantas > -- > http://rimantas.com/ Best, -- Marnen Laibow-Koser http://www.marnen.org [email protected] -- Posted via http://www.ruby-forum.com/. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~----------~----~----~----~------~----~------~--~---
