hmm this seems like more of a bug with Seafox

Sure.  But I didn't know the justification for why some Html5 elements 
got their own subclasses of WATagBrush and others only got a method on 
the WAHtmlCanvas.

I posted this here because it seemed to me that those additional 
subclasses may be more useful than only as a extension to the Seafox 
package.

The rule of thumb is everything that needs more methods than are on 
WAGenericTag gets its own subclass of WATagBrush. If WAGenericTag is enough 
then it's gonna be WAGenericTag.

Hi Philippe,

I've just got round to fixing some bugs in Seafox - namely trying to work out 
why:

<section>
 <header>
  <h1>foo</h1>
 </header>
 <p>bar</p>
</section>

gets translated as:

"Unrecognised element 'section'"
(html tag: 'section') with:[
"Unrecognised element 'header'"
(html tag: 'header') with:[
html heading level: 1; with: 'foo' ].
html paragraph: 'bar' ]

The reason is that WAHtmlCanvas>>#section and WAHtmlCanvas>>#header have an 
extra space or rather a CR at the end of their string, for example:  self tag: 
'header '

I guess that this isn't deliberate. Would you like me to correct it and check 
in a fixed version? The effected tags are:

summary
header
section
footer

In the meantime I'll add a call to #withoutTrailingBlanks to Seafox htmlElements

Cheers

Name: Seaside-HTML5-pmm.30
Author: pmm
Time: 24 January 2012, 7:24:43 am
UUID: a2ba133b-3076-4e57-9894-eb1d2f8afe4f
Ancestors: Seaside-HTML5-pmm.29

- Issue 701:    HTML5 Tags have superfluous space

Name: Seaside-HTML5-pmm.28
Author: pmm
Time: 24 January 2012, 7:30:51 am
UUID: 75c03738-39b6-4138-8857-2fd11a8ebb32
Ancestors: Seaside-HTML5-NickAger.26

- Issue 701:    HTML5 Tags have superfluous space