[svgwg] Issue: Define script element processong model marked as Needs WG input

• From: Nikos Andronikos via GitHub <sysbot+gh@w3.org>
• Date: Mon, 11 Jul 2016 02:10:18 +0000
• To: public-svg-issues@w3.org
• Message-ID: <issues.labeled-164747824-None-sysbot+gh@w3.org>

nikosandronikos has just labeled an issue for 
https://github.com/w3c/svgwg as "Needs WG input":

== Define script element processong model ==
SVG 2 has no details on how the script element is processed.

document.currentScript may return an SVGScriptElement, but we don't 
define how that is set.
See https://github.com/whatwg/html/pull/913

Need to do some analysis to determine what else is missing.
Ideally we would defer as much as possible to the HTML spec. I think 
this is intended by the statement currently in the SVG spec that says:

> A ‘script’ element is equivalent to the ‘script’ element in HTML

But that's not enough.



See https://github.com/w3c/svgwg/issues/196

Received on Monday, 11 July 2016 02:10:26 UTC