As far as EDGE goes there are two issues to consider...
First, technically there are two versions of Windows 10 out there. The original RTM and the November 2015 ver. 1511 "update". Each had a "base" version of Edge released with it. The RTM came with culmination of all the preview builds of Edge up to that time (I believe 12.10240 or sometimes 12.240). The November update briefly mirrored the RTM but soon upped Edge to 13.xxxxx within a week or so afterwards.
By now, the 30 day "gap" between those who upgraded to Windows before November 2015 (RTM) and those who upgraded afterwards (Ver. 1511) should be a moot point. In theory, anybody visiting windows update at any point after that November 2015 Update + ~30 days should be running the latest version of Edge all things being equal.
Second, All updates to Edge are cumulative. So unless a User has somehow gone against the norm and not allowed automatic updates nor manually updated themselves, in theory, they can still be running the RTM based version of Edge. Otherwise everybody using Windows 10 at any given moment should have the latest Edge running under that Windows 10 as well.
That said, in addition to the RTM version of EDGE currently whitelisted in the patch, shouldn't we probably add the current ver. 1511 Edge (13) user agent string (below) as well?
- Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/46.0.2486.0 Safari/537.36 Edge/13.10586
Overall, this will be a big honkin' waste of time and another reason to switch to browser feature detection instead of the traditional detection of the browser agent string. As soon as the next "branch" of Edge released (i.e. not a preview build), one if not both of the current strings in the test.js will be moot as the version is likely to become Edge/14.xxxxx.
- http://www.mydevice.io/ (used to verify current User Agent string)