I do realize that this might be a Microsoft Edge issue, rather than Discourse or any of the frameworks that Discourse is built on. It is also a fact that Win10M is a niche platform, with about 1% install base on the market. However, Microsoft is still keeping it alive, updates are rolled out promptly and they even have introduced new enterprise targeted products, like the HP Elite X3. Based on MSFT’s media comments, they are continuing to pursue the Enterprise market with W10M. I am reporting this for the sake of documentation and in hopes that perhaps Discourse core team has connections to Redmond?
The issue is reproducable with all Windows 10 Mobile devices. I have three different devices.
####Steps to reproduce:
- Browse a Discourse based website. Perhaps open links to new tabs, leaving the Discourse session to the background.
- End the browsing session. close Edge. Do something else.
- Re-open Edge and a tab with a session on a Discourse based site.
Often the Discourse session does not resume as expected. You may need to do a Reload on the website. Occasionally even this does not work and you get an empty page or error that site is not reachable. You may need to reload again, or sometime even close all browser tabs and browse back to the Discourse driven website.
When you finally get back there, the site again works OK.
Session is successfully resumed and view updated, if there are new posts on the site.