SVG 1.2 #2000

Open
MagixInTheAir opened this Issue Oct 4, 2015 · 4 comments

Comments

Projects
None yet
5 participants
@MagixInTheAir

SVG 1.2 support and statistics. pls. :D

@cvrebert

This comment has been minimized.

Show comment
Hide comment
@cvrebert

cvrebert Oct 5, 2015

Contributor

Erm, you mean SVG _Tiny_ 1.2? There's no plain SVG 1.2.
Apparently the major browsers only implement some bits and pieces from Tiny; see whatwg/html#126

Contributor

cvrebert commented Oct 5, 2015

Erm, you mean SVG _Tiny_ 1.2? There's no plain SVG 1.2.
Apparently the major browsers only implement some bits and pieces from Tiny; see whatwg/html#126

@MagixInTheAir

This comment has been minimized.

Show comment
Hide comment
@MagixInTheAir

MagixInTheAir Oct 5, 2015

Well, I read somewhere that is was impossible to have line-braks in SVG1.1 but it was possible in SVG1.2, I have no more experience with this. So I thought: "how supported is SVG 1.2?" and jumped to caniuse.com, found nothing, so opened an issue. I guess it's SVG Tiny 1.2, then 👍

Well, I read somewhere that is was impossible to have line-braks in SVG1.1 but it was possible in SVG1.2, I have no more experience with this. So I thought: "how supported is SVG 1.2?" and jumped to caniuse.com, found nothing, so opened an issue. I guess it's SVG Tiny 1.2, then 👍

@dstorey

This comment has been minimized.

Show comment
Hide comment
@dstorey

dstorey Oct 5, 2015

Contributor

I think 1.2 tiny was deprecated in favour of SVG2. Only Opera (I believe) implemented any substantial parts of 1.2 tiny (including the only named textArea that allowed line wrapping), and now Presto is dead (RIP) I'm not sure how useful this is? Probably should just break out the parts that are implemented on their own that are still on the standards track.

Contributor

dstorey commented Oct 5, 2015

I think 1.2 tiny was deprecated in favour of SVG2. Only Opera (I believe) implemented any substantial parts of 1.2 tiny (including the only named textArea that allowed line wrapping), and now Presto is dead (RIP) I'm not sure how useful this is? Probably should just break out the parts that are implemented on their own that are still on the standards track.

@tigt

This comment has been minimized.

Show comment
Hide comment
@tigt

tigt Oct 13, 2015

SVG is so big that you could make your own caniuse for it alone. Definitely shouldn't list new features under a unified banner like that.

tigt commented Oct 13, 2015

SVG is so big that you could make your own caniuse for it alone. Definitely shouldn't list new features under a unified banner like that.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment