-
-
Notifications
You must be signed in to change notification settings - Fork 4.3k
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.
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
SVG data attributes cause error in Edge #982
Labels
Comments
PaulBGD
changed the title
SVG data attributes cause error in IE
SVG data attributes cause error in Edge
Dec 6, 2017
Oh, Edge. You will never be a modern browser. This'll be easy to fix, but in the meantime you could workaround it by compiling with |
Thanks, I just removed the data attribute - it was added by the SVG tool :P
T
2017-12-06 14:40 GMT+01:00 Rich Harris <notifications@github.com>:
… Oh, Edge. You will never be a modern browser.
This'll be easy to fix, but in the meantime you could workaround it by
compiling with legacy: true — that causes (among other things)data-footo
becomenode.getAttribute('data-foo')rather thannode.dataset.foo`.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#982 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAM5P3CZr-f3CAdFtFhxn0KFfKG5CNymks5s9plngaJpZM4Q2BTY>
.
--
__________________
Tarjei Huse
Mobil: 920 63 413
|
fixed in 1.46.1 |
Thanks! |
<title> Is'nt SVG valid element. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi,
This example does not work in Edge:
https://svelte.technology/repl?version=1.44.2&gist=9c6e3507010663c0ef9e41901736c321
The problem was the attribute
data-name
. By removing it, I got the component to work in Edge. The error it gave was "Cannot set name on undefined or null reference".TLDR:
SVGs in components with data-xxx attributes seem to not work in Edge. See here for why:
https://developer.mozilla.org/en-US/docs/Web/SVG/Attribute/data-*
The text was updated successfully, but these errors were encountered: