- From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
- Date: Mon, 24 Sep 2018 19:47:18 +0000
- To: public-svg-issues@w3.org
The SVG Working Group just discussed `Identify SVG1 elements that are obsolete in SVG2`. <details><summary>The full IRC log of that discussion</summary> <AmeliaBR> Topic: Identify SVG1 elements that are obsolete in SVG2<br> <AmeliaBR> github: https://github.com/w3c/svgwg/issues/448<br> <AmeliaBR> Chris: Amelia, you linked to this link you made for your book, so that's a good start<br> <AmeliaBR> https://oreillymedia.github.io/Using_SVG/guide/markup.html#obsolete<br> <AmeliaBR> Amelia: Yes, though that's elements only.<br> <AmeliaBR> Chris: But that's most important to mention, since it affects the parser.<br> <AmeliaBR> ... so to start, a table of obsolete elements is useful, maybe linking to definitions in SVG 1.<br> <chris> generic svg elements, don't get treated as unknown container elelents. no-display, except altglyph falls back to generic tspan<br> <AmeliaBR> s/generic/Amelia: generic/<br> <AmeliaBR> Chris: I can post some introductory text on the issue for discussion<br> <AmeliaBR> ... Shouldn't prevent republishing CR (which we got our approval for today).<br> </details> -- GitHub Notification of comment by css-meeting-bot Please view or discuss this issue at https://github.com/w3c/svgwg/issues/448#issuecomment-424101306 using your GitHub account
Received on Monday, 24 September 2018 19:47:20 UTC