Cart
[Home] [By Thread] [By Date] [Recent Entries]
M. David Peterson wrote:
On Thu, 02 Aug 2007 18:06:09 -0600, Abel Braaksma <abel.online@xxxxxxxxx> wrote: I agree to all your points. When I put down that line I thought it was a bit too much of IE-blaming. FF has its quirks, definitely with XSLT-to-HTML in-place rendering (and even more definitely so when trying to use inline styles of a certain type, which don't get rendered, but is a bad design anyway, so who cares). About the spec thing, isn't it something from SGML heritage? I mean, didn't XML introduce the shortcut <br /> for <br></br> thus disallowing the SGML <br> on itself (without closing tag)? And wasn't it also SGML heritage that allowed <option selected> and XML forced more strict rules and made it <option selected="selected">? I didn't look at it like this before, but you have a strong point with your story on standards. Considering that the predecessor of IE was NCSA Mosaic (I believe MS bought them) which started out in 1992, way before XML. And even when XML came about, it was not immediately obvious that it would replace HTML. It was only way later that XHTML came about and by that time, browsers were already quite based on the HTML (read: SGML heritage) standards. And we're still struggling to get rid of our past ;) Cheers -- Abel Braaksma PS: I hoped that IE7 would be a huge overhaul, and MS claims to be rid of any NCSA Mosaic legacy code, but my experiences so far were quite disappointing when it came to rendering and standards (old/new doesn't matter) support.
|
