- From: Chris Lilley <chris@w3.org>
- Date: Tue, 2 Jun 2009 18:10:07 +0200
- To: SVG Working Group Issue Tracker <sysbot+tracker@w3.org>
- CC: public-svg-wg@w3.org
On Tuesday, June 2, 2009, 4:00:22 PM, SVG wrote: SWGIT> ISSUE-2275 (script_type_processing): Define processing for SWGIT> @type in script elements [SVG Core 2.0] SWGIT> http://www.w3.org/Graphics/SVG/WG/track/issues/2275 SWGIT> Raised by: Erik Dahlström SWGIT> On product: SVG Core 2.0 SWGIT> SVG 1.1 [1] and 1.2T [2] don't describe how @type on script SWGIT> elements affects script execution. SWGIT> Handling such as the one in HTML5[3] is allowed, but isn't SWGIT> required atm, though it's possible that we have tests that SWGIT> already depend on this particular behaviour. I agree that we should clarify this. It sees obvious (ie its not stated explicitly but probably should be) that scripts in unsupported languages are not executed. And indeed I added two tests for that (one for each method of labelling) to check that script which is labelled as being of an unknown (ie made up, bogus) type is not executed. SWGIT> We should consider defining how @type affects script processing in SVG. SWGIT> [1] http://www.w3.org/TR/SVG11/script.html SWGIT> [2] http://www.w3.org/TR/SVGTiny12/script.html SWGIT> [3] http://www.w3.org/TR/html5/semantics.html#running-a-script Incidentally, why is HTML5 making the default be text/javascript rather than application/ecmascript? However, the intent of the wording looks good in general and in particular, this part: If scripting is disabled for the script element, or if the user agent does not support the scripting language given by the script block's type for this script element, then the user agent must abort these steps at this point. The script is not executed. which is essentially what the two new tests are checking for. -- Chris Lilley mailto:chris@w3.org Technical Director, Interaction Domain W3C Graphics Activity Lead Co-Chair, W3C Hypertext CG
Received on Tuesday, 2 June 2009 16:10:15 UTC