You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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 whatwg/html#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
And I guess we just assume that SVG eventually defines steps to set the SVG script element's node document's currentScript value, and it's OK for now to have a return type which there's no normative text explaining how it takes that value?
The SVG Working Group just discussed Define script element processing model.
The full IRC log of that discussion
<AmeliaBR> Topic: Define script element processing model
<AmeliaBR> github: https://github.com//issues/196
<AmeliaBR> chris: domenic already said (in an HTML PR) what needs to be done. We can copy the HTML edits.
<AmeliaBR> … I think we should get something in the spec & then ask them to review.
<AmeliaBR> krit: I think the changes are (1) include the new mixin, and (2) reference the right section.
<AmeliaBR> … anyone willing to do the edits?
<AmeliaBR> chris: I could take a try, but not super familiar with the topic.
<AmeliaBR> Amelia: OK. You can always bring the issue back up if anything is unclear.
<AmeliaBR> … Do we need a resolution?
<AmeliaBR> krit: Wait until we have a proposed text.
<AmeliaBR> chris: The bits about currentScript, is that implemented or defined anywhere?
<AmeliaBR> Amelia: I think it's defined in HTML, just need to acknowledge that that can be an SVG script.
Activity
dirkschulze commentedon Jun 6, 2019
Question to the WG: What exactly do we need to specify?
AmeliaBR commentedon Jun 6, 2019
We probably need to find the exact algorithms & definitions in HTML to include by reference.
[-]Define script element processong model[/-][+]Define script element processing model[/+]svgeesus commentedon Jun 10, 2019
@domenic said:
see also the PR on html by @anne
css-meeting-bot commentedon Jun 17, 2019
The SVG Working Group just discussed
Define script element processing model.The full IRC log of that discussion
<AmeliaBR> Topic: Define script element processing model<AmeliaBR> github: https://github.com//issues/196
<AmeliaBR> chris: domenic already said (in an HTML PR) what needs to be done. We can copy the HTML edits.
<AmeliaBR> … I think we should get something in the spec & then ask them to review.
<AmeliaBR> krit: I think the changes are (1) include the new mixin, and (2) reference the right section.
<AmeliaBR> … anyone willing to do the edits?
<AmeliaBR> chris: I could take a try, but not super familiar with the topic.
<AmeliaBR> Amelia: OK. You can always bring the issue back up if anything is unclear.
<AmeliaBR> … Do we need a resolution?
<AmeliaBR> krit: Wait until we have a proposed text.
<AmeliaBR> chris: The bits about currentScript, is that implemented or defined anywhere?
<AmeliaBR> Amelia: I think it's defined in HTML, just need to acknowledge that that can be an SVG script.