These forums are currently read-only due to receiving more spam than actual discussion. Sorry.

It is currently Sat Dec 02, 2017 4:05 pm Advanced search

Blog's HTML is broken

Post any ideas for improving the WHATWG community website and forums.

Blog's HTML is broken

Postby JAB Creations » Thu May 12, 2011 10:22 pm

The WHATWG's blog is invalid (a paragraph) and it mixes HTML and XHTML link elements.

Which the W3C validator failed to catch. A self-closing element should be valid for XHTML though invalid for HTML, shouldn't it?
User avatar
JAB Creations
Posts: 566
Joined: Tue Mar 13, 2007 4:48 am
Location: Sarasota Florida, USA

Re: Blog's HTML is broken

Postby Xdega » Thu May 12, 2011 11:59 pm

The way I understood it, HTML will validate with self closing elements but is not recommended.

further explanation
Since the WHATWG blog is via WordPress...
I will say this, given that I have used WordPress, and for the most part find it very useful as a quick,simple blog framework.
The problem is that WP insistently force formats your posts in to XHTML markup (which it the current markup that WordPress uses last I checked).

I guess a quote that somewhat backs this up is on the :whatwg: WHATWG Wiki: ... _or_.3E.3F
Should I close empty elements with /> or >?
Void elements in HTML (e.g. the br, img and input elements) do not require a trailing slash. e.g. Instead of writing <br />, you only need to write <br>. This is the same as in HTML4. However, due to the widespread attempts to use XHTML1, there are a significant number of pages using the trailing slash. Because of this, the trailing slash syntax has been permitted on void elements in HTML in order to ease migration from XHTML1 back to HTML.

It's much of the same issue we have with the forums. They are built in XHTML, we can edit parts of the STATIC code/markup but some of the deeper parts of the application will remain XHTML. Especially the parts that are dynamically created, like posts/comments.

I think the biggest issue here although being wrong in terms of markup, is that we are using third party frameworks that do not yet support true HTML and are still using XHTML.

Until we/WHATWG can find the time and resources to build an entire web based infrastructure from scratch, we can't really complain about frameworks formatting parts of our applications in less-recommended markup.

That being said, I would be first to sign up and help in any way possible if WHATWG were to start an official movement to unify all of the web based community resources in to true and proper HTML. In other words a new,complete professional website with all of the current recourses in one place.
The experience personally for me would be great as I work on my Comp Sci. degree and career goals.
But it is of course a relatively huge project with several applications needing to be created (Forums, Blogs, Online reading of Mailing list, Spec documentation, etc). Would take a team of developers/testers to ensure safe/secure applications.

/end ;)
Posts: 124
Joined: Tue Mar 01, 2011 6:30 pm
Location: USA

Return to Website Feedback and Ideas

Who is online

Users browsing this forum: No registered users and 1 guest