On Tue, Apr 10, 2018 at 3:58 AM, Jeff Gilbert <jgilb...@mozilla.com> wrote:
> Do we have a heuristic for when to /not/ include something from HTML in SVG?
> More or less, these additions to SVG just strike me as having solid
> potential risk (for both spec-interaction and implementation bugs) and
> negligible upside. Do we have people asking for this?

Microsoft and the SVG WG seem to be driving this somewhat. I think
there's mostly upsides to having HTML and SVG share more code as it
means ongoing maintenance will be more shared as well. It seems it
might also lead to some simplification on the SVG side (e.g., a
further change being considered is to make target a simple string
rather than an animated string).

OP did not mention this, but the idea is that pretty much everything
would end up being defined in HTML:

dev-platform mailing list

Reply via email to