HTML5 Redefines Footer

It seems like only yesterday that the HTML5 Super Friends asked the HTML5 working groups to rethink footer’s content model to avoid web developer misuse and frustration. Okay, it wasn’t yesterday, it was Monday. Close enough. Today comes word that footer is indeed being redefined as we requested. This is a wonderful usability improvement to HTML5, and we salute the working group(s) for listening and acting.

38 thoughts on “HTML5 Redefines Footer

  1. Wow! It seems like the Super Friends can get anything done (In under a few days).

    I’m happy to see footer has been re-defined. Now if only the Super Friends could make Internet Explorer do an ‘about face’ in the same amount of time I’d really be impressed.

    Ps. Evertime I see this, I remember the South Park episode with the ‘Super Best Friends’. Great episode.

  2. Now that the Superfriends have been proven effective lobbyists, can y’all start lobbying Microsoft to pledge to fully support HTML5+CSS3 ASAP?

  3. Does this mean that the HTML5 footer is now an appropriate place for blog comments? I suppose not if header or footer elements cannot be nested within. article elements are the most appropriate for marking up an individual comment:

    This could be a forum post, a magazine or newspaper article, a Web log entry, a user-submitted comment, an interactive widget, or any other independent item of content.

    Anyway, it doesn’t matter where such comment articles appear, as long as they are nested within the blog post article:

    When article elements are nested, the inner article elements represent articles that are in principle related to the contents of the outer article. For instance, a Web log entry on a site that accepts user-submitted comments could represent the comments as article elements nested within the article element for the Web log entry.

  4. This is why the W3C’s close model of spec development sucks and the WHATWG’s open model is awesome. Under the W3C’s control, we’d find out when it’s too late. Under WHATWG’s control, you just need the right person to make some noise and things can get better overnight. I’m very glad that the W3C let the WHATWG keep things running the way they like it.

  5. The change to “footer” was made due to a request sent to the mailing list before you posted your feedback.

    If you want your feedback to affect the spec, you need to post it to the mailing list. Right now I’ve been told that you are still working on it, getting feedback from your blog post readers and facebook friends, so it has not entered the HTML5 feedback cycle yet.

    I cannot emphasise this enough: If you want to contribute to HTML5, please either e-mail me, e-mail one of the mailing lists, or file a bug (either directly, or using the bug reporting form at the bottom of the window when viewing the spec). While I do try to follow feedback on blog posts, it is not the way to send detailed feedback and it will likely not result in changes to the spec unless the feedback is highlighting a security problem or something obviously and unarguably wrong.

  6. Robert:

    Under WHATWG’s control, you just need the right person to make some noise and things can get better overnight.

    Only if it’s what the browser vendors want ;)

  7. Pingback: RSS
  8. My two cents, but I’m just really glad to see the orange back again.
    Now maybe I can make use of all those color-appropriate pics I took centering around said color…
    >:)

  9. If you want your feedback to affect the spec, you need to post it to the mailing list.

    We’ve posted the following to the mailing list:

    * Comments on the content model of small.

    * Comments on the content model of footer (now resolved).

    * Comments on using legend within details and figure.

    I’ve also written directly to Hixie about naming convention inconsistencies; Hixie resolved them, and the W3C working group followed suit within a day or two.

    So we’re good.

  10. Jeffrey: I would encourage you to join the HTML Working Group. In return for agreeing to the patent policy, you will be subscribed to the W3C mailing list and get to participate in polls, votes, and other activities that will determine whether or not this draft is ready for Last Call.

    There is no requirement that you attend any meetings, join any teleconferences, or even post to the mailing list, ever.

  11. I’d actually like to comment on your latest entry, but you’ve disabled comments for it. I came here to see if you’ve updated about HTML5 again, and would have normally browsed away seeing a personal story, but it was actually very interesting.

    Sometimes very strange things come up at the table and you think, “How can no one have mentioned this important detail before?” Great story.

  12. I’m eager to see the finished product, but I won’t be one to twiddle my thumb waiting. Why not just wait, what’s all the excitement about html, it will get finished we will read and we will apply it.

  13. So what? While you all celebrate what HTML 5 MIGHT support, and what it MIGHT do, we here in the land of FLASH/AS3/HAXE/HARDWARE ACCELERATION, are busy MAKING applications that can do practically anything. Will HTML 5 ever support DIRECT X? Will it ever support per pixel manipulation of bitmaps? Will it ever support computing and visualizing data inside of a slick and highly portable interface?

    NO.

    Now, if you want to build yer little blog, and have a gay old time talking about how great HTML 5 is and maybe someday post a video that plays in 1/3rd of the worlds browsers without using the dreaded Flash (we know you’re just scared of programming) then go right on ahead on with your HTML 5, it’ll suit you just fine.

Comments are closed.