HTML5 and RenderLoopContinuation

Oh sure I just meant that if that's what it takes to actually emit valid html5 pages from within seaside then maybe it should/could be part of the #beHtml5 method in the default Seaside-HTML5 package so everyone can use it without  having to find this thread.

I just don't know enough to be able to discern whether the changes to the root you posted cover everything that needs to be done or not.

Anyways. Thanks for posting it

On Nov 22, 2012, at 1:10 PM, "Boris Popov, DeepCove Labs" <[hidden email]> wrote:

> Paul,
>
> No specific reason other than that we use a common library to configure our roots to avoid unnecessary method overrides.
>
> -Boris
>
>
> -----Original Message-----
> From: [hidden email] [mailto:[hidden email]] On Behalf Of Paul DeBruicker
> Sent: Thursday, November 22, 2012 4:08 PM
> To: Seaside - general discussion
> Subject: Re: [Seaside] HTML5 and RenderLoopContinuation
>
> Is there any reason to not make the #beHtml5 method do all the things in your configuration?
>
>
>
>
> On 11/22/2012 05:18 AM, Boris Popov, DeepCove Labs wrote:
>> Tobias,
>>
>> 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'.
>>
>> -Boris
>>
>>
>> -----Original Message-----
>> From: [hidden email] [mailto:[hidden email]] On Behalf Of Tobias Pape
>> Sent: Thursday, November 22, 2012 5:08 AM
>> To: Seaside - general discussion
>> Subject: [Seaside] HTML5 and RenderLoopContinuation
>>
>> Hi
>>
>> I just played with Seaside and HTML5,
>> however, the resulting html is not HTML5 compatible.
>> The validator says
>>    Line 2, Column 249: Bad value Content-Script-Type for attribute http-equiv on element meta.
>>
>> which is the result of
>>
>> WARenderLoopContinuation>>updateRoot:
>>    "..."
>>    anHtmlRoot meta contentScriptType: WAMimeType textJavascript.
>>    anHtmlRoot htmlAttributes
>>        at: 'xmlns' put: 'http://www.w3.org/1999/xhtml';
>>        at: 'xml:lang' put: 'en';
>>        at: 'lang' put: 'en'.
>>    "..."
>>
>> The content script type is incorrect as of HTML5.
>> (see answer here:
>>    http://stackoverflow.com/questions/6320084/why-is-meta-http-equiv-content-script-type-mostly-unused#8864160
>> ).
>> Also, 'xml:lang' is accepted for compatibility only, and 'xmlns' is incorrect for
>> HTML5 too (while silently ignored).
>>
>> Long story short, can we optionalize this part?
>> I can work around the xml:lang and xmlns-attributes in a subsequent #updateRoot: but I cannot undo the content script type without editing WARenderLoopContinuation>>updateRoot:
>>
>> If you want to, I can try to come up with something.
>>
>> Best
>>    -tobias
>>
>>
>> _______________________________________________
>> seaside mailing list
>> [hidden email]
>> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
>> _______________________________________________
>> seaside mailing list
>> [hidden email]
>> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
>>
>
> _______________________________________________
> seaside mailing list
> [hidden email]
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
> _______________________________________________
> seaside mailing list
> [hidden email]
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
_______________________________________________
seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside

Paul DeBruicker wrote

> Oh sure I just meant that if that's what it takes to actually emit valid
> html5 pages from within seaside then maybe it should/could be part of the
> #beHtml5 method in the default Seaside-HTML5 package so everyone can use
> it without  having to find this thread.

Are there any plans to make HTML5 the standard output for Seaside instead of
XHTML 1.0 Strict at any time in the future? (I would love this :)