[Seaside] Seaside elements vs. HTML5 spec

[David Buck]

The HTML5 spec is still changing and it's hard to keep up with the 
latest changes.  Since I'm developing a Seaside course, I decided to go 
through the current HTML5 spec (Editor's Draft 23 September 2011) and 
compare what element tags are available in that spec versus the tags we 
support in Seaside (Seaside 3.0 - 8 released with VW7.8).  In general, 
Seaside has quite good support for HTML5.  Here are the differences I've 
found:

Note:  I'm simply offering this list as information for anyone 
interested.  I needed to research this for the course and thought it 
would be good to share the results.

The following tags are inconsistent between Seaside and the current 
version of HTML5
    mark   (already reported)

Tags in HTML5 not supported by Seaside (some of these are poor style and 
should use newer tags but are still supported in HTML):
    hgroup
    figcaption
    s
    i (should use emphasis)
    b (should use strong)
    u (shouldn't really use at all)
    bdi
    bdo
    wbr
    embed
    audio (interestingly, a WAAudioTag class exists with no call from 
the canvas)
    track
    map (WAImageMapTag class uses an anchor tag)
    area
    output
    summary

The following tags are supported by Seaside but aren't in the current 
HTML5 spec (no problem keeping them for backward compatibility but 
perhaps they should be marked as deprecated):
    rubyBase
    rubyBaseContainer
    rubyTextContainer
    datagrid
    acronym
    dialog
    teletype

David Buck