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
Currently I don't believe there's any sanctioned way to update the contents of an SVG script element (assuming #483 is done so the protection covers them too).
The spec says that we recommend authors use script.textContent, script.innerText or script.text for updating the contents of a script element with a trusted object. Should the same not also hold true for an SVG script element?
As far as I can see this isn't just a spec issue it's also missing from Chrome's implementation.
It would seem to make sense to shadow Node.textContent to the SVGScriptElement type?
The text was updated successfully, but these errors were encountered:
We should probably define some kind of mixin the two script elements can share. But this doesn't seem like a high priority as you can just use the HTML script element in all cases.
Currently I don't believe there's any sanctioned way to update the contents of an SVG script element (assuming #483 is done so the protection covers them too).
The spec says that we recommend authors use script.textContent, script.innerText or script.text for updating the contents of a script element with a trusted object. Should the same not also hold true for an SVG script element?
As far as I can see this isn't just a spec issue it's also missing from Chrome's implementation.
It would seem to make sense to shadow Node.textContent to the SVGScriptElement type?
The text was updated successfully, but these errors were encountered: