[svgwg] Issue: Define script element processong model (#196) marked as Agenda+

• From: Dirk Schulze via GitHub <sysbot+gh@w3.org>
• Date: Thu, 06 Jun 2019 12:18:03 +0000
• To: public-svg-issues@w3.org
• Message-ID: <issues.labeled-164747824-None-sysbot+gh@w3.org>

dirkschulze has just labeled an issue for https://github.com/w3c/svgwg as "Agenda+":

== 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 Thursday, 6 June 2019 12:18:04 UTC