Compatibility with next Edge release (will have external SVG content support)

[jonathantneal]

Compatibility with next Edge release (will have external SVG content support)

[fvsch]

Asked about the UA again: https://twitter.com/fvsch/status/641962573408153600

tl;dr, expect the Edge token version to increment with platform feature payloads (in the future, when they hit preview). We'll also update the Chrome token version to reflect tested interoperability for sites that sniff on the Chrome version. The current set of platform updates will be Edge/13.[build] when they hit the Consumer branch

Looking at the current regexp, which contains \bEdge\/12\b, we should be safe and since Edge/13 will have support for external content, barring any bug in Edge's implementation or a different issue in svg4everybody, svg4everybody 2.0.0 should work as-is in Edge/13 with no need for an update.

I suggest keeping this issue open until we can actually test it, of course.

[jaydenseric]

Hi guys, just pointing out:

SVG external content shipped in EdgeHTML 13 as part of the Microsoft Edge version included in Windows 10 build 10586 (November 2015).

– Admin, Windows Developer

[fvsch]

I verified that Edge 13 works well with SVG external content, and that svg4everybody doesn’t get in the way (on a production website that uses an external SVG sprite + svg4everybody, and on a simple test page without svg4everybody).

The README is up-to-date as well, so I’m closing this issue, as there is nothing to be done.