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?

Are there privacy concerns from embedding pings (et al) in images? I
suppose we better have been handling CORS requests from within SVGs
properly already, so it should Just Work?

On Mon, Apr 9, 2018 at 6:26 PM, Cameron McCormack <> wrote:
> On Tue, Apr 10, 2018, at 7:56 AM, Jeff Gilbert wrote:
>> Can we not put more things into SVG? Making SVG more complicated seems
>> like it should be an anti-goal for the web platform.
> I think we should align the features and behavior of HTML <a> and SVG <a>.
>   <!DOCTYPE html>
>   <a href=...>something</a>
>  <svg>
>    <a href=...><path ... /></a>
>   </svg>
> I don't see why the two DOM objects for the HTML <a> and SVG <a> should 
> behave substantially differently.
dev-platform mailing list

Reply via email to