Re: Minutes, SVG WG Brussels f2f day 4 (Monday)

>
> shepazu: MSIE considered novel syntax... HTMl5 is some way from being done
> and the parsing algo has only 1 implementaitn thats incomplete
> ... from W3C process perspective its far from done
>

I believe Henri Sivonen's implementation (which powers validator.nu, which
is enabled by default in Firefox nightly builds, and which we plan to ship
as the HTML parser in the next Firefox release) is quite complete.

Adam Barth and Eric Seidel are working on an independent implementation for
Webkit (I don't know if they're going to tackle the SVG support, though).

<AlexD> Are there any tests for HTMl5 parsing conformance?
>

Yes, here:
http://gsnedders.html5.org/html5lib-tests/runner.html
Those tests include tests of SVG-in-HTML5 (in test10.dat and test11.dat).

<AlexD> Given how long it will take HTML5 to mature (i.e. PREC) then perhaps
> SVG needs to take some lead in an HTML(4)+SVG integration profile... HTML5
> is a bit of vapourware right now really.
>

Not at all, see above.

pdengler: can a div work in a co ordinate space/
> ... when do we decide this is a div/
> ... like a div within SVG
> ... what does it mean to have HTML not as a foreign object in SVG?
> ... we are yet to dicover what people expet and how they will use SVVG in
> HTML
> ... remove the idea of forign object..?
>

Currently in HTML5 you still need to use <foreignObject> to wrap HTML in
SVG. Using a "naked" HTML element in SVG will actually cause the parser to
exit SVG-mode. This is done for Web compatibility reasons: there are Web
pages out there that contains randomly-mixed chunks of SVG and HTML.

It would be great if we can extend the HTML parser spec to allow eliding
<foreignObject> in some situations in the future, but that may be precluded
by the Web compatibility issues.

Rob