Noissue - Always show "Install" button for Microsoft Edge

static/js/index.js

 (function()
 {
   var visibleTab;
   var container;
 
   window.toggleMore = function()
   {
     if (container.className == "hidden")
       container.className = visibleTab || getDefaultTab();
     else
@@ skipping 21 matching lines @@
     checkEdgeSupport();
   }
 
   function checkEdgeSupport()
   {
     if (!window.navigator.userAgent)
       return;
 
     var content = document.getElementById("content");
     var match = window.navigator.userAgent.match(/Edge\/\d+\.(\d+)/);
-    if (match && match[1] >= 14361 && content.classList.contains("edge"))
+    if (match && match[1] >= 15063 && content.classList.contains("edge"))

[Oleksandr, 2017/09/12 00:25:57]

It's outside the scope of this change, but I just noticed that this also
captures Microsoft Edge on Xbox, which we do not support. Based on this the
User-Agent is very similar: https://ctrl.blog/entry/xbox-edge-user-agent. Same
goes for Windows 10 Mobile, which we don't support either. I don't think it's a
big deal, just FYI.

[Sebastian Noack, 2017/09/12 00:58:20]

What would users see on XBox and Windows Phone, when they click the
ms-windows-store:// link? If they see a message that the app is not supported on
their advice, this might be a better user experience than hiding the link and
telling them that they need the Creators Update (which they don't).

[juliandoucette, 2017/09/12 11:47:17]

I second Sebastian's question. Can you test this?

I think that we should create an issue to identify these edge cases and display
an appropriate message.

[Oleksandr, 2017/09/12 17:20:08]

I am actually fairly confident Windows Store would handle this. Unfortunately I
have neither Xbox nor Windows 10 Mobile phone. I can only assume the Store will
say the application isn't supported on this device, because we have explicitly
set our package is available only on PC. But I have no way of testing this.

       content.classList.add("edge-supported");
   }
 
   init();
 })();