- From: Fredrik Söderqvist via GitHub <sysbot+gh@w3.org>
- Date: Wed, 04 Dec 2019 11:17:26 +0000
- To: public-svg-issues@w3.org
I suppose we're fine with the element remaining in the spec given it's current status. Given that a fairly large portion of the spec is supported across all major browsers (at least unreleased versions) these days, it seems a bit of a pity keep bits that is unlikely to see implementations mixed in. I suspect that a "proper" streaming implementation would require additional knobs to be practically useful. On the "implementation complexity" part, based on the two `<discard>` implementations I've worked on (Blink and Presto), the following commonalities spring to mind: 1. `<discard>` is timed element but not an animation element. 2. Yanking stuff out of the document (and most of the time also destroying it) is apparently more complicated than people (me included) like to think. (1) was less of an issue for SVG Tiny 1.2 (as implemented by Presto) which had other such elements (`<svg:video>` and `<svg:audio>`). (2) can be made less severe by mechanisms like proper garbage collection of "internal" objects, but removing elements also tend to have a cascade of side-effects (notifiers etc.), which can turn up other problems besides memory issues from element destruction. Now let the "you n00b, I can implement `<discard>` 14 times while locked in a box, using only a pencil" tirade commence... -- GitHub Notification of comment by fsoder Please view or discuss this issue at https://github.com/w3c/svgwg/issues/717#issuecomment-561600321 using your GitHub account
Received on Wednesday, 4 December 2019 11:17:28 UTC