Re: SVG SMIL news from Google
Amelia Bellamy-Royds <[email protected]> Wed, 17 Aug 2016 15:12:40 -0600
| Newsgroups | gmane.comp.web.svg |
|---|---|
| Message-ID | <CAFDDJ7yZ-HT5c2fz1Ghdt84EMQmf-g5b3U+UGJZQM0btGdFEwg@mail.gmail.com> |
--94eb2c0977ecf35097053a4aeccf Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable This is good news, even if it's only a stay of execution for now. A note to all, a few weeks back the SVG WG resolved [1] to publish a proper working draft of the stand-alone SVG Animation Elements specification [2]. This replaces the animation chapter from SVG 1.1, instead of including an animation chapter in the core SVG 2 spec. There are a few technical clean-ups that need to happen first (the spec markup currently doesn't play nice with the new W3C stylesheets) but that is the first step towards moving forward on modernizing SMIL-style SVG Animations and making them fully compatible with the Web Animations framework. Philip, in your note on the forum you mention that next steps include "Proposing removal of pieces of SMIL that don=E2=80=99t enjoy widespread use." We'll = keep an eye out for new issues tagged "SVG Animations" in the SVGWG repo [3]. However, if the Chrome team is devoting resources to identifying specific issues with SVG Animations, I'm sure that Brian Birtles would appreciate any help in cleaning up that spec and polishing it off; he has understandably put in on the back burner this past year since the original Chrome deprecation announcement. ~ABR [1]: https://www.w3.org/2016/08/04-svg-minutes.html#resolution02 [2]: https://svgwg.org/specs/animations/ [3]: https://github.com/w3c/svgwg/issues --94eb2c0977ecf35097053a4aeccf Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable <div dir=3D"ltr">This is good news, even if it's only a stay of executi= on for now.<div><br></div><div>A note to all, a few weeks back the SVG WG r= esolved [1] to publish a proper working draft of the stand-alone SVG Animat= ion Elements specification [2].=C2=A0 This replaces the animation chapter f= rom SVG 1.1, instead of including an animation chapter in the core SVG 2 sp= ec.</div><div><br></div><div>There are a few technical clean-ups that need = to happen first (the spec markup currently doesn't play nice with the n= ew W3C stylesheets) but that is the first step towards moving forward on mo= dernizing SMIL-style SVG Animations and making them fully compatible with t= he Web Animations framework.</div><div><br></div><div>Philip, in your note = on the forum you mention that next steps include "<span style=3D"line-= height:17px;font-family:Arial,Helvetica,sans-serif;font-size:13px">Proposin= g removal of pieces of SMIL that don=E2=80=99t enjoy widespread use." = =C2=A0We'll keep an eye out for new issues tagged "SVG Animations&= quot; in the SVGWG repo [3].=C2=A0 However, if the Chrome team is devoting = resources to identifying specific issues with SVG Animations, I'm sure = that Brian Birtles would appreciate any help in cleaning up that spec and p= olishing it off; he has understandably put in on the back burner this past = year since the original Chrome deprecation announcement.</span></div><div><= br></div><div>~ABR</div><div><br></div><div>[1]:=C2=A0<a href=3D"https://ww= w.w3.org/2016/08/04-svg-minutes.html#resolution02">https://www.w3.org/2016/= 08/04-svg-minutes.html#resolution02</a></div><div>[2]:=C2=A0<a href=3D"http= s://svgwg.org/specs/animations/">https://svgwg.org/specs/animations/</a></d= iv><div>[3]:=C2=A0<a href=3D"https://github.com/w3c/svgwg/issues">https://g= ithub.com/w3c/svgwg/issues</a></div></div> --94eb2c0977ecf35097053a4aeccf--