Re: Point of Extensibility

Ah, thanks Doug! :)

I didn't think about comments in comment.

I have now posted this solution as "Proposal 4: XML inside comments" on the
wiki, with a few updates that might solve the comment-in-comment issue and
also some new reasons why this solution might not fly:

http://wiki.whatwg.org/wiki/Extensions#Proposal_4:_XML_inside_comments

Problem now: It's even more klunky!! :-D

Regards

Eirik Mikkelsen

On 4/3/08, Doug Schepers <schepers@w3.org> wrote:
>
> Hi, Eirik-
>
> Eirik Mikkelsen wrote (on 4/3/08 9:55 AM):
>
> >
> > This is my first post to this list, and I've just been pondering this
> > problem for a few hours.
> >
>
> Welcome to the deep end of the pool.  :)
>
>
>   - Easy for authors to understand, even if the syntax is a bit ugly
> >
>
> If by the syntax, you mean the element names, those aren't necessarily the
> real names. <fallback> could be <alt>, or whatever.  We'll need to survey
> all the element names in the wild, and choose the shortest, most distinctive
> and easily understood one available.
>
>
>
>  Here's an example:
> >
> > <div id="myMathFallback">2x</div>
> > <!--[if accept text/mathml]>
> >  <math xmlns="http://www.w3.org/1998/Math/MathML">
> >     <mn>2</mn>
> >     <mi>x</mi>
> >  </math>
> >
> >  <script type="text/javascript">
> >     document.getElementById('myMathFallback').style.display = 'none';
> >  </script>
> > <![endif]-->
> >
>
> My immediate concern with this (besides the fact that I think it looks
> klunky) is that inline comment blocks in the content will break it.
>
> <!--[if (accept text/mathml) & (accept image/svg+xml)]>
>  <svg xmlns="http://www.w3.org/2000/svg">
>     <ellipse cx="300" cy="150" rx="200" ry="80"/>
>     <!--
>     <path d="M0,10 C100,10 120,50"/>
>     -->
>  </svg>
> <![endif]-->
>
> It would require extra sanitization on the part of authors.
>
> Regards-
> -Doug Schepers
> W3C Team Contact, SVG, CDF, and WebAPI
>