You are reading a single comment by @Velocio and its replies. Click here to read the full conversation.
  • Semantic markup. It's not that I want full HTML5 support, but rather that I want to reduce layout/structural HTML in favour of descriptive markup.

    Example, instead of

    some text
    I'd rather have some text. The latter actually describes what is inside it, the former doesn't and requires additional class matching in the browser.

    I'd like to have something that is transitional, and very ready for a strict HTML5 when the time comes, but for the meantime I'm fine with shifting some of this to CSS so that the HTML can be made more semantic.

    LFGSS is XHTML already, but I want to remove the garbage HTML... so much of it is still based on HTML2 or 3 techniques (i.e. table layouts, lots of nesting), and I want an HTML5 approach to show through as this actually results in less nesting... the sooner I can close a top-level nest the quicker a browser can layout and render that part of the code and the sooner something appears on the end users screens.

    So my HTML5 quest is about taking what is really good about HTML5 and that which is supported or possible in XHTML making it available now so that we get those benefits.

    If you look at LFGSS, the entire page is wrapped in a table. Were that to go it would perform the render way faster.

About

Avatar for Velocio @Velocio started