W3C home > Mailing lists > Public > spec-prod@w3.org > October to December 2013

Re: ReSpec 3.2

From: Leif Halvard Silli <xn--mlform-iua@xn--mlform-iua.no>
Date: Mon, 21 Oct 2013 04:59:53 +0200
To: shane@aptest.com
Cc: Robin Berjon <robin@w3.org>, "spec-prod@w3.org" <spec-prod@w3.org>
Message-ID: <20131021045953028414.09430929@xn--mlform-iua.no>
Shane,

for whatever reason (may be Robin already fixed it?), I don't have that 
issue in my particular file, anymore - the CDATA start and end 
declaration is kept, and nothing is added if it wasn't in the source 
code.

Btw, if you were to "force" the advice of those compat guidelines onto 
CDATA declaration, then it would only match when <style> and <script> 
use their default MIME types *and* the <style>/<script> content matches 
those MIME types . But if e.g. <script> is used as e.g. a 
template/markup code container, then it can be more complex. 

Leif H


Shane McCarron, Sun, 20 Oct 2013 21:04:54 -0500:
> Okay - I am on it.  I suspect that the browsers (some anyway) are going to
> strip the CDATA nodes out.  I might end up just injecting the best practice
> CDATA into each relevant section (style and script) as per
> 
http://www.w3.org/MarkUp/2010/ED-xhtml-media-types-20100218/#compatGuidelines

> in
> guideline A.4
> 
> 
> On Sun, Oct 20, 2013 at 1:46 PM, Robin Berjon <robin@w3.org> wrote:
> 
>> On 19/10/2013 12:49 , Leif Halvard Silli wrote:
>> 
>>> Robin Berjon, Fri, 18 Oct 2013 14:19:42 +0200:
>>> 
>>>>    • If the browser supports it, the saving dialog now uses the
>>>> download attribute on <a> to trigger a real download of the generated
>>>> output, as "Overview.html". For browsers that don't support that yet,
>>>> you can nevertheless right click the button and save link as. In both
>>>> cases this is faster than the previous methods.
>>>> 
>>> 
>>> Regarding the options for saving as XHTML5 and XHTML1, then both of
>>> them remove any CDATA declarations that might occurs inside <style> or
>>> <script>. As result, if <style> or  <script> contains “<” or “&”, the
>>> semantics of are changed from when they occurred inside CDATA. (If it
>>> is a goal to remove unnecessary CDATA declarations, then Polyglot
>>> Markup describes when it is safe to do so.)
>>> 
>>> For HTML5 output, the CDATA declaration remains after saving.
>>> 
>> 
>> The HTML5 output mode pretty much just saves what the browser has using
>> innerHTML. The XML modes have to be handcrafted.
>> 
>> I don't personally have an interest in supporting the XML modes, but I
>> will certainly take patches.
>> 
>> 
>> --
>> Robin Berjon - http://berjon.com/ - @robinberjon
>> 
>> 
> 
> 
> -- 
> Shane P. McCarron
> Managing Director, Applied Testing and Technology, Inc.
Received on Monday, 21 October 2013 03:00:22 UTC

This archive was generated by hypermail 2.3.1 : Monday, 21 October 2013 03:00:22 UTC