WorryFree Computers   »   [go: up one dir, main page]
Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Define script element processing model #196

Open
nikosandronikos opened this issue Jul 11, 2016 · 4 comments
Open

Define script element processing model #196

nikosandronikos opened this issue Jul 11, 2016 · 4 comments
Assignees
@svgeesus
Labels
Interactivity chapter Needs editing SVG Core
Milestone
SVG 2.0 Proposed ...

Comments

@nikosandronikos
Copy link
Member

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

But that's not enough.
@nikosandronikos nikosandronikos added this to the CR 2 milestone Jul 11, 2016
@boggydigital boggydigital modified the milestones: SVG Core clean-up, SVG 2.1 Working Draft Jun 11, 2018
@dirkschulze
Copy link
Contributor

Question to the WG: What exactly do we need to specify?

@AmeliaBR
Copy link
Contributor
AmeliaBR commented Jun 6, 2019

We probably need to find the exact algorithms & definitions in HTML to include by reference.

@svgeesus svgeesus changed the title Define script element processong model Define script element processing model Jun 10, 2019
@svgeesus
Copy link
Contributor
svgeesus commented Jun 10, 2019 •
edited

@domenic said:

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?

see also the PR on html by @anne

@svgeesus svgeesus self-assigned this Jun 17, 2019
@css-meeting-bot
Copy link
Member

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.

@koto koto mentioned this issue Jan 25, 2024
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@svgeesus svgeesus

Labels
Interactivity chapter Needs editing SVG Core
Projects
None yet
Milestone
SVG 2.0 Proposed Recommendation
Development

No branches or pull requests
6 participants
@boggydigital @dirkschulze @svgeesus @nikosandronikos @AmeliaBR @css-meeting-bot