W3C home > Mailing lists > Public > www-svg@w3.org > December 2004

Re: LC Comment - Script & Progressive Rendering / Multiple Pages

From: Jim Ley <jim@jibbering.com>
Date: Wed, 1 Dec 2004 20:55:48 -0000
To: www-svg@w3.org
Message-ID: <colb4l$3fe$1@sea.gmane.org>


"Boris Zbarsky" <bzbarsky@MIT.EDU> wrote in message 
news:41AE2A2A.2070709@mit.edu...

> (Not to mention issues like trying to execute a JavaScript 1.2 script from 
> inside JavaScript 1.3 and so forth... eval really does not cut it there).

It's a really bad idea to even begin to think of doing that IMO, and SVG 
only requires ECMAScript Ed.3, and as there's no mime-type for JavaScript 
1.2 it can't be specified in SVG (of course it's inadvisable to use 1.2 on 
the web seen as not all UA's respect the language tag to really mean 
JavaScript1.2 anyway.)

> Very well.  Provide an alternate solution to the use cases this solves, 
> then?  URIRequest and eval really don't cut it there.

a new element rendered with sXBL that brings in the script, or a new image 
element that brings in the script, much like we do now in HTML with IFRAMEs. 
The script method is not recommended in HTML, so why we want to introduce 
this mess into SVG I don't know.  One of the continued complaints is the 
complexity of SVG 1.2, lets keep it simple, and not include hundreds of 
words to even begin to define the behaviour in this case.  You've already 
shown how complicated it is to begin to define it (even before we have 
externalResourcesRequired / defer to consider)

Cheers,

Jim. 
Received on Wednesday, 1 December 2004 20:55:54 GMT

This archive was generated by hypermail 2.3.1 : Friday, 8 March 2013 15:54:29 GMT