Comments on: Null end tags in XHTML http://www.webdevout.net/tidings/2006/08/09/null-end-tags-in-xhtml/ Updates on the march of progress. A weblog about web design, standards, web browsers, and the overall health of the Web. Wed, 14 Dec 2011 14:45:24 +0000 http://wordpress.org/?v=2.8.4 hourly 1 By: David Hammond http://www.webdevout.net/tidings/2006/08/09/null-end-tags-in-xhtml/comment-page-1/#comment-3933 David Hammond Tue, 20 Feb 2007 14:08:05 +0000 http://www.webdevout.net/tidings/2006/08/09/null-end-tags-in-xhtml/#comment-3933 The XHTML spec only suggests a space to maximize (but not guarantee!) compatibility with older user agents such as Netscape 4. It isn't required, only strongly encouraged if you're sending the page as <code>text/html</code>. The XHTML spec only suggests a space to maximize (but not guarantee!) compatibility with older user agents such as Netscape 4. It isn’t required, only strongly encouraged if you’re sending the page as text/html.

Posted using Mozilla Firefox 2.0.0.1 on Linux.

]]> By: Asher Gabara http://www.webdevout.net/tidings/2006/08/09/null-end-tags-in-xhtml/comment-page-1/#comment-3932 Asher Gabara Tue, 20 Feb 2007 05:41:30 +0000 http://www.webdevout.net/tidings/2006/08/09/null-end-tags-in-xhtml/#comment-3932 "Despite common practice, a space before the “/” character wouldn’t change this." Actually, the <a href="http://www.w3.org/TR/xhtml1/#C_2" rel="nofollow">XHTML spec</a> says to include a space. In addition, <a href="http://lists.webjunction.org/wjlists/xml4lib/2002-January/004755.html" rel="nofollow">omitting the space removes compatibility with Netscape 4</a>. Still, what you said is obviously correct. “Despite common practice, a space before the “/” character wouldn’t change this.”

Actually, the XHTML spec says to include a space. In addition, omitting the space removes compatibility with Netscape 4.

Still, what you said is obviously correct.

Posted using Mozilla Firefox 2.0.0.1 on Windows.

]]> By: David Hammond http://www.webdevout.net/tidings/2006/08/09/null-end-tags-in-xhtml/comment-page-1/#comment-1122 David Hammond Thu, 10 Aug 2006 14:54:03 +0000 http://www.webdevout.net/tidings/2006/08/09/null-end-tags-in-xhtml/#comment-1122 The parser/syntax highlighter will be an integrated part of the Web Devout rewrite I'm working on. It'll be used to highlight source in various new articles, and I plan to somehow implement it into the <a href="http://www.webdevout.net/test.php" rel="nofollow">webpage test</a> system as well. It's being written in PHP because that's the primary language used on this site, although output will be cached to improve performance. I'm currently using Ubuntu Dapper Drake and GNOME. I use Wine to test Internet Explorer 4 through 6, and I run IE7 in a VMware virtual machine with Windows XP (yes, I bought a legitimate copy). These days, Ubuntu is pretty much the leader in desktop Linux, and it's a really solid distro. KDE isn't bad as a desktop environment, but it proved way too unstable for me (especially the sound system). GNOME has worked great for me. The parser/syntax highlighter will be an integrated part of the Web Devout rewrite I’m working on. It’ll be used to highlight source in various new articles, and I plan to somehow implement it into the webpage test system as well. It’s being written in PHP because that’s the primary language used on this site, although output will be cached to improve performance.

I’m currently using Ubuntu Dapper Drake and GNOME. I use Wine to test Internet Explorer 4 through 6, and I run IE7 in a VMware virtual machine with Windows XP (yes, I bought a legitimate copy). These days, Ubuntu is pretty much the leader in desktop Linux, and it’s a really solid distro. KDE isn’t bad as a desktop environment, but it proved way too unstable for me (especially the sound system). GNOME has worked great for me.

Posted using Mozilla Firefox 1.5.0.6 on Linux.

]]> By: Wulf http://www.webdevout.net/tidings/2006/08/09/null-end-tags-in-xhtml/comment-page-1/#comment-1120 Wulf Thu, 10 Aug 2006 05:09:38 +0000 http://www.webdevout.net/tidings/2006/08/09/null-end-tags-in-xhtml/#comment-1120 <blockquote cite="David Hammond">"I am currently finishing up writing an SGML / XML parser and syntax highlighter..."</blockquote> Cool. Any idea on a release date? Also, the comment system says you're running Linux. If you don't mind me asking, what <abbr title="distribution">distro</abbr> (and <acronym title="Desktop Environment">DE</acronym>) are you using? [Until Wine gets better] I'm planning on setting up a dual-boot system, but I can't seem to decide on a distro & DE... BTW: Awesome site :)

“I am currently finishing up writing an SGML / XML parser and syntax highlighter…”

Cool. Any idea on a release date?

Also, the comment system says you’re running Linux. If you don’t mind me asking, what distro (and DE) are you using? [Until Wine gets better] I’m planning on setting up a dual-boot system, but I can’t seem to decide on a distro & DE…

BTW: Awesome site :)

Posted using Mozilla Firefox 2.0b1 on Windows.

]]> By: David Hammond http://www.webdevout.net/tidings/2006/08/09/null-end-tags-in-xhtml/comment-page-1/#comment-1119 David Hammond Wed, 09 Aug 2006 18:24:19 +0000 http://www.webdevout.net/tidings/2006/08/09/null-end-tags-in-xhtml/#comment-1119 Because so many websites are written like XHTML but sent as <code>text/html</code>, no practical web browser can safely support null end tags in HTML without resulting in a bunch of greater-than signs spewed over the pages. Only user agents that are more true to the SGML standard support them. Off-hand, I know the W3C HTML validator supports them, as you can see if you set the option to display the parse tree. Some other classic SGML user agents (not necessarily web browsers) also support it. I am currently finishing up writing an SGML / XML parser and syntax highlighter which properly supports null end tags, empty tags, unclosed tags, and some other lesser-known features of SGML. The reason few user agents support it is not likely difficulty of implementation, but rather legacy and real world compatibility reasons. Because so many websites are written like XHTML but sent as text/html, no practical web browser can safely support null end tags in HTML without resulting in a bunch of greater-than signs spewed over the pages. Only user agents that are more true to the SGML standard support them. Off-hand, I know the W3C HTML validator supports them, as you can see if you set the option to display the parse tree. Some other classic SGML user agents (not necessarily web browsers) also support it. I am currently finishing up writing an SGML / XML parser and syntax highlighter which properly supports null end tags, empty tags, unclosed tags, and some other lesser-known features of SGML. The reason few user agents support it is not likely difficulty of implementation, but rather legacy and real world compatibility reasons.

Posted using Mozilla Firefox 1.5.0.6 on Linux.

]]>