[Seaside] RE: HTML5 and RenderLoopContinuation

Boris Popov, DeepCove Labs boris at deepcovelabs.com
Fri Nov 23 15:15:27 UTC 2012


WAMetaElement>>encodeBeforeOn: aDocument
 super encodeBeforeOn: aDocument.


-----Original Message-----
From: seaside-bounces at lists.squeakfoundation.org [mailto:seaside-bounces at lists.squeakfoundation.org] On Behalf Of Helene Bilbo
Sent: Friday, November 23, 2012 6:24 AM
To: seaside at lists.squeakfoundation.org
Subject: [Seaside] RE: HTML5 and RenderLoopContinuation

Boris Popov, DeepCove Labs (SNN) wrote
> This is what we do in our shared library class to configure all roots 
> for HTML5,
> aHtmlRoot beHtml5.
> aHtmlRoot headElements copy do: [:ea | (ea isKindOf: WAMetaElement)
> ifTrue: [aHtmlRoot headElements remove: ea]].
> (aHtmlRoot htmlAttributes)
>     addClass: 'no-js';
>     removeKey: 'xmlns';
>     removeKey: 'xml:lang';
>     removeKey: 'lang'.
> aHtmlRoot headElements addFirst: ((WAMetaElement root: aHtmlRoot)
>             attributeAt: 'charset' put: 'utf-8';
>             yourself).
> (aHtmlRoot meta)
>     responseHeaderName: 'X-UA-Compatible';
>     content: 'IE=edge,chrome=1'.    

Hi, thank you, this works nice, but for some reason it produces:

<meta charset="utf-8" content="">

which is not valid ("Attribute content not allowed on element meta at this point."), instead of:

<meta charset="utf-8" />

Has anybody a hint, how to change this?

View this message in context: http://forum.world.st/HTML5-and-RenderLoopContinuation-tp4656351p4656468.html
Sent from the Seaside General mailing list archive at Nabble.com.
seaside mailing list
seaside at lists.squeakfoundation.org

More information about the seaside mailing list