OS: Windows 10 Tech Preview
Xojo: Xojo 2015r1
Steps: Just found an annoying problem under Windows 10 Tech Preview : when Project Spartan, the new browser, is set as default it is impossible to run a Web Edition project.
One gets the message ‘Can’t reach this page’.
I also tried http://locahost:8080 and I get a search on bing for that.
Don’t bother reminding me your policy ‘no support for beta versions of the system’. I am simply trying to help, not asking for a fix.
Try 127.0.0.1 instead
You know why they call it spartan right? It’s for the last 300 still using Internet Explorer.
:X
Spartan - showing or characterized by austerity or a lack of comfort or luxury
Awesome choice of names 
However I have seen this with other versions of IE
Use 127.0.0.1 and see if that resolves proprly
For what it’s worth, I tried Spartan with my compiled web app with success. I did not notice any obvious abnormal behavior. I was actually quite favorably impressed with the new MS browser, still in development and only in technical preview. It should be noted that Spartan is a completely revamped browser, that is not backwards compatible with IE, is the most standards compliant browser ever issued by MS. It is going the default browser in Windows 10. IE 11 will be offered for backwards compatibility.
According to this article, there may actually be slightly more than 300 users of IE. As a Chrome user myself, I was a bit surprised with the statistics. That said, I appreciate the humour.
From what I’ve seen it should be a decent effort
Its not clear how much of a a rewrite this is since they’ve said it uses the same engine as IE 11 then said others that seem very contradictory
http://www.zdnet.com/article/microsofts-spartan-browser-whats-under-the-hood/
So I dunno
That said its not the first time I’ve seen a URL using localhost invoke a bing search
It would not be a Microsoft browser without a little quirck, would it? Seriously, I would think that the release version will have this one fixed.
[quote=178853:@Phillip Zedalis]You know why they call it spartan right? It’s for the last 300 still using Internet Explorer.
:X[/quote]
Eat hearty, lads, for tonight we dine in Vista!
On Longhorn ?
Sometimes the jokes write themselves.
By default, the IDE points to 127.0.0.1:8080, that is what triggers the ‘Can’t reach the page’. That is why I tried localhost afterward.
I tried as well, and indeed it works quite fine with apps already on the server.
It is not the end of the world. Any current browser does fine for development.
Just tried connecting to the built in Windows localhost (Internet Information Services) with IE, works just fine. Spartan cannot connect to it either. I reported it.
I confirm that with the current Windows 10 build No 10130, Xojo Web does not work in debug run with Edge (formally Project Spartan) as default browser.
I tried to build a standalone, which still does not work. It does in IE or Chrome.
Could be a problem when Windows 10 comes to market in a bit more than a month…
Could you clarify what “does not work” means?
The issue I had reported back in April : <https://xojo.com/issue/38858>
The app simply never shows in either debug run or standalone mode. The error is :
The app displays fine in all other browsers.
Same thing with a standalone built app.
I suspected some sandboxing issue analogous to what happens with iOS Safari, but a local html file or a PDF open fine.
Suggests Spartan is having “some” issue if every other browser can display it
Esp when Spartan says it it reach the URL
FWIW, there are users complaining about this issue on the Microsoft forums, so I doubt this is our bug…
According to this post:
You can type about:flags and check the Allow Localhost Loopback to get this working again (on build 10166 and later)
[quote=199834:@Greg O’Lone]
According to this post:
You can type about:flags and check the Allow Localhost Loopback to get this working again (on build 10166 and later)[/quote]
Thanks. I am in the process to download the 10166.
The most important part is :
[quote]
I work on the Microsoft Edge team. This is a known issue that we are currently looking into. Jonathan Sampson Jun 9 at 7:21[/quote]
OK. I applied the remedy that way :
After that, Edge will work just fine to run web apps.