-
Facebook hacked! All Web Services at Risk
July 25, 2008
-
Firebug Lite 1.2; Now with improved lite-ness
July 25, 2008
-
HTML 5 Linking all around the horn
July 25, 2008
-
Download Free "JavaScript Reference Guide" eBooks
July 25, 2008
-
Blogger: Digg Icon automatically appears on all your posts
July 25, 2008
-
Intersections and SVG objects
July 25, 2008
- Paolo: I hope you’ll try this other game, KABOOM, a spaceship browsergame.
- ralph: Thats pretty cool.
- Sean P. Aune: Glad you enjoyed the post:) Yes, it was a ton of work, but well worth it!
- alpha: Thanks for the inclusion!
- Wesam Saif: This is very similar to the NoGray Color Picker http://www.nogray.com/color_pi cker.php
- July 2008
- June 2008
- May 2008
- April 2008
- March 2008
- February 2008
- January 2008
- December 2007
- November 2007
- October 2007
- September 2007
- August 2007
Internal IE-HTML DOM still isn’t XHTML compliant
Jon Davis was glad to see that XHTML compliance was on the list in IE 8, but was surprised to see the above. It turns out that he found:
XHTML compliance exists in parsing and rendering only. Microsoft is still using an internal IE-HTML DOM that is not XHTML-compliant, even in XHTML documents. All you have to do prove this out is, in script, alert(document.documentElement.outerHTML); and what do you see? The most obvious observation is a total disregard for XHTML 1.0 § 4.2, which reads, “Element and attribute names must be in lower case; XHTML documents must use lower case for all HTML element and attribute names. This difference is necessary because XML is case-sensitive e.g. <li> and <LI> are different tags.” Why does this matter? It matters because of DHTML. It matters because there is an implemented and oft-used setter on DOM elements’ innerHTML. It matters because people actually use the DOM programmatically, both in evaluating and assigning markup. It matters because the browser has a Content-Editable mode that is often used with online content editing whereby the innerHTML contents are posted to the server for viewing as content. It matters because Internet Explorer has a COM interface that can, and often is, used to parse and tidy HTML markup, or to provide a WYSIWYG rich text editor for applications. It matters because it’s broken, has been all along, and has never been deemed acceptable.
Should IE be looking to fix this?
Read more on the source site
No comments yet.
feel free to leave a comment
Comment Guidelines: Basic XHTML is allowed (a href, strong, em, code). All line breaks and paragraphs are automatically generated. Off-topic or inappropriate comments will be edited or deleted. Email addresses will never be published. Keep it PG-13 people!
XHTML: You can use these tags: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <code> <em> <i> <strike> <strong>
All fields marked with " * " are required.
