Re: [Xsltforms-support] CSS style Output and SVG (IE 8, Firefox and Chrome)

[COUTHURES A. <ala...@ag...>]

Hello David,

Cross-browser SVG sizing is still not well supported in XSLTForms. I'm 
afraid it won't be a priority soon. SVG within XSLTForms has just been 
considered as a proof case for graphs generated from graph2svg.xsl at 
client-side 
http://www.svgopen.org/2010/papers/14-Dynamic_SVG_graphs_for_XForms/.

About SVGWeb, I have to admit I was disappointed. With graphs again, the 
rendering wasn't as good as with native SVG, especially about dotted 
lines. The XML document has to be in the default namespace because 
prefix use is not supported, not even "svg:". I proposed my own patch 
for prefix support but it was rejected by the SVGWeb team 
http://code.google.com/p/svgweb/issues/detail?id=454 :-(

Are you in a hurry about good SVG sizing support?

Thanks!

-Alain

Le 03/03/2011 23:17, David French a écrit :
>
> I am trying to output an SVG image through xlstforms clientside 
> (following the example of http://en.wikibooks.org/wiki/XForms/SVG).
>
> With Firefox 3.6 ,Firefox 4.0 and Chrome, nothing I do seems to affect 
> the size of the output resulting in horizontal and vertical sliders 
> being applied when actual image is larger than space assumed. A 
> minimal test example is available here 
> http://soundings01.appspot.com/xsltforms/xfsvg4.xml
> The default image size also varies depending on browser. Chrome shows 
> a smaller portion of the image than Firefox (4 beta 12). Inspecting 
> the element in Chrome shows span.xforms-value of 300x19.
>
> IE 8 appears to be constrained by the style width and height so that 
> if the width/height are less than the image dimensions the top left 
> corner of the image alone is visible with no sliders added (see 
> http://soundings01.appspot.com/xsltforms/xfsvg5.xml) but if the image 
> is smaller than the styling width height, the full image is seen. The 
> rendering appears to be done by silverlight in this instance.
>
> I am looking for consistent behaviour and a better understanding of 
> how to work around any differences. Any pointers?
> Thanks
> David
>