Project Spartan and the Windows 10 January Preview Build
Yesterday, we announced that Windows 10 will ship with a brand new browser, codenamed “Project Spartan.” Designed for Windows 10, Spartan provides a more interoperable, reliable, and discoverable experience with advanced features including the ability to annotate on web pages, a distraction-free reading experience, and integration of Cortana for finding and doing things online faster.
Spartan is a single browser designed to work great across the entire Windows 10 device family - from keyboard and mouse on the Windows 10 desktop to touch, gestures, voice, controllers and sensors.
Powered by a new rendering engine, Spartan is designed for interoperability with the modern web. We’ve deliberately moved away from the versioned document modes historically used in Internet Explorer, and now use the same markup as other modern browsers. Spartan’s new rendering engine is designed to work with the way the web is written today.
Like Windows 10 itself Spartan will remain up-to-date: as a service, both providing new platform capabilities, security and performance improvements, and ensuring web developers a consistent platform across Windows 10 devices. Spartan and the new rendering engine are truly evergreen.
Spartan provides compatibility with the millions of existing enterprise web sites designed for Internet Explorer. To achieve this, Spartan loads the IE11 engine for legacy enterprise web sites when needed, while using the new rendering engine for modern web sites. This approach provides both a strong compatibility guarantee for legacy enterprise web sites and a forward looking interoperable web standards promise.
We recognize some enterprises have legacy web sites that use older technologies designed only for Internet Explorer, such as custom ActiveX controls and Browser Helper Objects. For these users, Internet Explorer will also be available on Windows 10. Internet Explorer will use the same dual rendering engines as Spartan, ensuring web developers can consistently target the latest web standards.
What does this mean to web developers?
If you are building a public consumer-facing web site here’s what you need to know:
- Our new rendering engine will be the default engine for Windows 10, Spartan, and Internet Explorer. This engine has interoperability at its core and consumes the same markup you send other modern browsers. Our standards support and roadmap can be found at https://status.modern.ie.
- Public Internet web sites will be rendered using the new engine and modern standards, and legacy Internet Explorer behaviors including document modes are not supported in the new engine. If your web sites depends on legacy Internet Explorer behaviors we encourage you to update to modern standards.
- Our goal is interoperability with the modern web and we need your help! You can test the new engine via the Windows Insider Program or using https://remote.modern.ie. Please let us know (via Connect or Twitter) when you find interoperability problems so we can work with the W3C and other browser manufacturers to ensure great interoperability.
New features and fixes in the January Insider Update
On Friday, we’re also rolling out a new preview build to Windows 10 Insiders. This new preview will also be available on RemoteIE soon. This build doesn’t have Project Spartan yet, but does have lots of updates to the new web rendering engine that Spartan will use. We started testing our new rendering engine by rolling it out to a portion of Insiders using the Windows Technical Preview in November.
Since that time, we’ve received over 12,000 feedback reports through the smiley face icon alone. This new build has over 2000 changes to the new platform, largely influenced by that feedback. In addition to many fixes, there are also several new platform features we are thrilled to be releasing in the updated preview:
- HTTP Strict Transport Security (HSTS) — an HTTP headerto inform the browser to always request a given domain over SSL, reducing MITM attack surface area.
- HTTP Live Streaming (HLS) and Dynamic Adaptive Streaming over HTTP (DASH) –expands our plugin-free adaptive video streaming to support the popular HLS and DASH protocols.
- Video Tracks — adds the ability to get information about multiple video tracks, and switch between them using the VideoTrack.selected attributes.
- DOM L3 XPath – initial support for accessing the DOM tree using the XPath syntax. Expanded support will come in a future release.
Additionally, you’ll find updated F12 developer tools that include the updated UI we shipped to IE11 users last month as well as several new features and improvements. Here’s a few of our favorites:
- New and Improved Network Tool—capture and debug network traffic with new UX and capabilities, such as auto-start, a content type filter, and error highlighting.
- HTML & CSS Pretty Printing— just as you’ve been able to nicely reformat minified JavaScript in the debugger, you’ll now be able to do this for HTML and CSS.
- Async Callstacks for Events and Timers— quickly view the “async callstack” to connect the dots between event dispatch and the original addEventListener call or between setting a timer and the timer being fired.
- Sourcemaps for Styles and in the Memory Profiler— jump to your original sources, such as TypeScript or SASS, directly from the Styles pane or Memory Profiler tools.
- Find Reference and Go To Definition— jump directly to a function call’s definition or find the references to a given variable.
With these improvements, we’re increasing the number of Insiders that get the new engine as we work towards this as the default for all users. If you’re curious and want to opt-in now, remember to navigate to about:flags and set “Enable Experimental Web Platform Features” to Enabled.
We’re excited to share our continued progress with you and to introduce Project Spartan to the Microsoft family. Please continue to share your feedback via Twitter, UserVoice (feature requests) and Connect (bug reports) and help shape our next browser. We’ll also be holding our next Twitter #AskIE session on Tuesday, January 27th from 10AM-12PM PST so you can ask questions to the team. See you there!
— Jason Weber, Group Program Manager, Internet Explorer
Comments
Anonymous
January 22, 2015
Congrats guys, this is looking like a amazing release!Anonymous
January 22, 2015
May I ask what the new Browser UI is rendered in? Is it Win32 GDI, WPF, WinRT XAML, HTML/CSS, D2D custom rendering, DirectUI.... I am really looking forward to trying it out for myself! Thanks DanielAnonymous
January 22, 2015
Does the new Network tool export to standard formats (e.g. JSON-based HTTP Archive format - HAR) or popular ones (Session Archive Zip)? Does the new Network tool offer network emulation (e.g. bandwidth limits, latency simulation, etc)? Can you share details about your privacy choices for HSTS: blogs.msdn.com/.../https-everything-in-2015-with-free-certificates-and-hsts.aspx Any statement on the removal of P3P Support? Any news on whether Tracking Protection Lists will be supported? Will the old MJPEG streaming format (supported by other browsers, used by some webcams) be supported too? Will the Spartan effort include new web services (e.g. view my favorites list somewhere on OneDrive or whatnot)? Will there be new Fish-themed demos? When will Spartan be declared the final name and not just a code-name? Do we need to keep our lighters lit, or will we get this encore even if we don't? Will IE8's HTML5 implementation bugs around localStorage and postMessage be fixed? Can Desktop application developers using the WebOC today use the Spartan engine? Will Spartan run in Enhanced Protected Mode by default?Anonymous
January 22, 2015
I'm most curious to know if Spartan will support Group Policy templates for IT administrators (beyond Enterprise Mode lists and existing IE templates). After that, I'd like to know more about extensions/plugins and also the UserAgent string of Spartan.Anonymous
January 22, 2015
@EricLaw, I kinda hope they keep the Spartan name. Between HoloLens and Cortana and Spartan, it's good to see Microsoft learn how to name things. ;)Anonymous
January 22, 2015
^ Yep, totally agree that they should keep the Spartan name as the final one. Make it so!Anonymous
January 22, 2015
Shame on mobile there are both bars at the top (address bar) and bottom (app bar with commands). The clean simplicity of IE on WP 8.1 was great.Anonymous
January 22, 2015
Where's the Mac version?Anonymous
January 22, 2015
Please stop developing browsers and concentrate on phasing out IE. Take a page out of Netscape's book and stop development. You lost and it's time to face that fact. I'm not trying to be rude or sarcastic. Please consider this approach. Sincerely, Web Application Developers EverywhereAnonymous
January 22, 2015
Will the async call stack support also work for promises?Anonymous
January 22, 2015
Just wondering if you all were ready to discuss the web app/extension model? Will WinJS be part of it and what is the story for developers making extensions and add ons for FireFox and Chrome?Anonymous
January 22, 2015
@Web Application Developers Everywhere Any sentence that starts with "I'm not trying to be rude...". You don't even know anything about the new browser, what qualifies you to comment on this at all?Anonymous
January 22, 2015
This article really didn't help clear up anything for me. Both browsers will include both rendering engines and will default to the modern engine. So what makes them different exactly? Is the difference only that IE loads ActiveX controls and Browser Helper Objects while Spartan does not? And how does it determine when to change between the modes? Can the mode switch depending on the page or is it on the whole site? What makes the new version different from the old other than it will support auto-updating to add new features? Beyond that it sounds like a typical new IE release with new features being added and the ability to fall back to older modes if that is necessary.Anonymous
January 22, 2015
The comment has been removedAnonymous
January 22, 2015
All of these questions and more answered at https://status.modern.ie/ EXCEPT, when can we expect a VM image with spartan on it on modern.ie so we can give the browser a trial run and provide proper feedback? Also, can we really not step away from the past yet? MSFT have labeled IE 5.5 EOL for ages, even having broken from tradition with IE11 by rendering in standards mode and turning off non-standard javascript APIs in it by default. Why would MSIE need to support an IE11 rendering engine which should behave the same as Spartan, a project which presumably has the same or better standards support, unless... wait, is this browser just IE5.2 for the mac wrapped in a new shell? TRICKY TRICKY!Anonymous
January 22, 2015
This looks like chrome. Please contribute to chrome if you want to make the web browser better. All this does is increase development costs by having to support another browser. Enough damage has been done by IE. Please stop development. http://www.chromium.org/Anonymous
January 22, 2015
@ Web Application Developers Everywhere If you're going to ask them to do a Netscape, they actually are. Because born out of the ashes of Netscape was Firefox, which ran on a fork of Netscape's layout engine. It is the same with IE and Spartan. It would be very dangerous for the Open Web if Microsoft decided to just use Blink or WebKit.Anonymous
January 22, 2015
Totally agree to keep the name Spartan. Probably you already own it. But regard the Spartan visual I'm missing the transparent chrome over there. In the mobile version I think you are stolen too much space. The actual version is just a minimum bar in the bottom. You are using the top AND the bottom now. Please at least make the bottom just "...". But I really like the way it is now.Anonymous
January 22, 2015
So... this basically means Spartan will be available only for Win 10? I really hope not. That would just be dumb, literally giving away market share to... ugh... Chrome. The older OSes (especially Vista/2008) could well use a newer browser, and I'm sure Win 7/2008R2 users probably wouldn't mind one, either.Anonymous
January 22, 2015
The comment has been removedAnonymous
January 22, 2015
@ Why & Web Application Developers Everywhere No, sane developers don't want a single engine. People want different engines that pushes each other forward, make things in a standard way (not like Chrome) and allows to check if the problem is their code or a bug in the browser. MS, please keep up with all the recent work and don't forget to provide Spartan directly to Windows 7 & 8.1 because we all know that many people won't upgrade their OSAnonymous
January 22, 2015
@Sardoc: I suspect the hope is that everyone on Win7 will take advantage of the free upgrade to Windows 10. That may be ... optimistic.Anonymous
January 22, 2015
Looks great, however I'm missing full support for webcomponents. What about "Spartan"-apps?Anonymous
January 22, 2015
@Josh, agree to a point. I think the danger is that the web becomes stagnant due to a virtual need to provide legacy on older versions of IE. MSFT is effectively trying to give people no rational reason not to upgrade to a newer browser, but the reality is older systems that haven't upgraded to the latest system are mostly from china or aged hardware which cannot upgrade to a newer version of windows. Aside from that, many (virtual) machines running IE5.5-8 are automated systems like bots.Anonymous
January 22, 2015
The comment has been removedAnonymous
January 22, 2015
The comment has been removedAnonymous
January 22, 2015
rss feeds didn't automatically update in the last release, will they work in the next release of windows 10?Anonymous
January 22, 2015
@Why, Based on your reasoning, Chromium should never have come about in the first place. Other browsers already existed prior to Chromium being developed, and its development required people to support another browser. Would you similarly reject out of hand any other browser development work that is not Chromium, or do you reserve that for Microsoft? Do you also go around to anyone developing versions of Linux other than your favorite one, telling them to not bother?Anonymous
January 22, 2015
Just as hopeful that those users would download a new browser.. they don't exist on the web either, Vista?.. Windows Server?.. cmonAnonymous
January 22, 2015
What I really don't get is, why, if IE and Spartan are going to share the new and old engines, both browsers are going to be available in Windows 10? Are not they going to be almost the same? At least in the way they present the web?Anonymous
January 22, 2015
You CAN NOT put the address bar at top for the phone UI! NO WAY!Anonymous
January 22, 2015
So in following suit are they going to renamed the "Administrator" account to "MasterChief"??!Anonymous
January 22, 2015
Hector, i wonder the same: "Spartan loads the IE11 engine for legacy enterprise web sites when needed, while using the new rendering engine for modern web sites." "Internet Explorer will use the same dual rendering engines as Spartan, ensuring web developers can consistently target the latest web standards." Sounds to me they will basically be the same, but different UI/name. So more of a marketing thing?Anonymous
January 22, 2015
Since XAML+C# has to be protected, there is limited support for HTML5. No vision for the future of the User Interface. Legacy support for Forms, WPF, Silverlight, just to name a few of the "succesfull" UX'sAnonymous
January 22, 2015
It's a natural thing because main support has ended but will Windows 7 be an end indeed in IE11? But the person who says "He also wants you to offer it to Windows 7."may be in the inside, too. I think so in the heart actually, too.Anonymous
January 22, 2015
Address bar on top is big mistake. Try to use that on 5" screen device (e.g. Lumia 930) with one hand.Anonymous
January 22, 2015
I agree with everyone who's disappointed at seeing the address bar on top in the Phone UI. As a Lumia 1520 owner, having to reach to the top of the screen to navigate elsewhere is not very comfortable.Anonymous
January 22, 2015
Chrome trolls, please go use Chrome while the rest of us enjoy healthy competition to move the web forward while keeping Google from dominating browsers. Spartan looks great. But - I sincerely hope that you simply name it IE 12 and then rename the legacy IE to something like IE (Legacy) and not install it by default. Otherwise, you are going to face a bunch of confused users. That being said, congrats on bringing IE's UI up to date - I hope there's a new extension model, because that was horrible in the old IE. Also, I have to agree that the mobile UI doesn't look good - there's too much wasted space.Anonymous
January 22, 2015
The comment has been removedAnonymous
January 22, 2015
And one more thing - what about developer tools in Spartan? Does it include the much-improved F12 tools from IE 11? If not, it definitely should.Anonymous
January 22, 2015
Gotta agree with everyone else here. PLEASE move the address bar back to the bottom on mobile. That's one of the best things about IE11 on Windows Phone today.Anonymous
January 22, 2015
Please move the address bar to the bottom for mobile/phabletAnonymous
January 22, 2015
The comment has been removedAnonymous
January 22, 2015
I know you probably will just name it as Modern IE as well, but I think that the address bar on the bottom was really nice even on desktop/tablet windows 8.1, please put the address bar back on the bottom! thanksAnonymous
January 22, 2015
The comment has been removedAnonymous
January 22, 2015
I realy do hope microsot keep the name Spartan. It's already bludering the internet and becomming a famous name. I like and I bet a lot of you do too!Anonymous
January 22, 2015
dAnonymous
January 22, 2015
Address bar top position no!!! Please move to bottom!! Address bar.Anonymous
January 22, 2015
Your days of comfortably accessing me are over. I will no longer serve the tyranny of the user.Anonymous
January 22, 2015
Under "Links" in the segment "IE Sites" you find "Exploring IE" which points to windowsteamblog.com/ie/b/ie/ This link is dead! Please remove it!Anonymous
January 22, 2015
There is no need for another rendering engine. And I hope (but don't believe in) that the first step people will do after installing Windows is to install either Chrome or Firefox. @arizdev: >> To those saying contribute to Chrome/Webkit, that is a backhanded slap in the face of hard working people on the IE dev team There is nothing bad about slapping in the face of people from IE dev team. They should look to get a job where they can do something useful.Anonymous
January 22, 2015
The comment has been removedAnonymous
January 22, 2015
Looks fantastic. However, I'm concerned you are throwing away some of the proper design of Windows Phone apps in that I have to get my thumb to the top of the phablet screen to enter something in the address bar. This type of poor design is typical of iOS and Android apps and is being widely copied. One of the worst incarnations of this is the burger menu button at the top right of apps or mobile web sites, bit at they are on the right, whereas your refresh button is tip left. Can we have an option to move the address bar to the bottom of the screen on mobile?Anonymous
January 22, 2015
图标蛮好看的。Anonymous
January 22, 2015
Shame on mobile there are both bars at the top (address bar) and bottom (app bar with commands). The clean simplicity of IE on WP 8.1 was great. Dude you seriously should make Spartan easier to use on the mobile platform. A UI like this would anger tons of Mobile IE lovers. Just put the address bar on the bottom, and hide the app bar by default, please!Anonymous
January 22, 2015
WEBRTC...anything on that..?Anonymous
January 22, 2015
I think project Spartan winner when:
- Maximum support html5 and css3
- Support extensions and apps in store
- Easy develop extensions with visual studio javascript and c# project template that can access cortana , .net, office and services
- Voice commands such as scroll up and down , close tabs and more
- Advanced and comfortable developer tools
- Automatic and partial update
- Themeable and advanced options(flags)
- Cross platform and mac, Linux, android and other versions
Anonymous
January 22, 2015
Please implement content wrapping based on zoom level of the page like Opera or Dolphin has.Anonymous
January 22, 2015
Can i instal on windows xp sp2 32 bit? :DAnonymous
January 22, 2015
Don't call it Internet Explorer! LET IT DIE! Spartan is the future! (Call it Spartan! One word names are cool!)Anonymous
January 22, 2015
Everyone is preferring currently Chrome because of its speed. Even with Windows XP it's 100x faster than newest IE11 on Windows 8.1 (jQuery DOM/append/offsetWidth, etc) Please make Spartan as fast as possible for HTML5 and JS and you're my heros. Maybe even some jQuery Native Support? Keep on the good work. Best decision to leave IE11 as it is and go for a new browser.Anonymous
January 22, 2015
Feel free to ask, and to rejoice? Produced another ***, as we say. Maybe it's time to reconsider the concept or simply abandon this venture? Marketers 5 points ... sold at the price of a regular update the product.Anonymous
January 22, 2015
Will we be able to add/edit styles from the F12 tools like you can in Chrome? That is a must feature!Anonymous
January 22, 2015
The comment has been removedAnonymous
January 22, 2015
Sorry, it is "weak" not "week"Anonymous
January 22, 2015
The comment has been removedAnonymous
January 22, 2015
The comment has been removedAnonymous
January 22, 2015
I strongly suggest to keep just one engine in Spartan...new rendering engine for modern web sites....Including more then one rendering engine will lead to big confusion. For Compatibility there is IE 11......Enterprises will use IE 11 for legacy web sites and Spartan for all modern sites. Keep it simple.Anonymous
January 22, 2015
Also for Mobile version of Spartan...Please move the address bar to the bottom like IE on WP 8.1....This is better as it will be easy to use one handed on 4inch to 6+ inch phonesAnonymous
January 22, 2015
The comment has been removedAnonymous
January 22, 2015
Will Spartan support ShadowDOM and WebComponents ? It's the most important new web tech I'm waiting for. It's like WPF for HTML ( see polymerproject.org )Anonymous
January 23, 2015
please add Spartan to https://remote.modern.ie/Anonymous
January 23, 2015
I sure hope you're adding a touch gesture to rapidly return to the top of a long page (and/or rapidly scroll to the bottom). With the number of "infinitely scrolling" web pages out there (Facebook, Twitter, many Tumblr layouts, etc., etc.) it's extremely tedious -- ESPECIALLY on the Phone, but also on the Surface -- to endlessly flick just to get back to the top or down to the bottom. PLEASE consider doing something amazing like adding "semantic zoom" to be able to shrink the extending rendered portion of the page down to fit on the screen, and then just touch where you want to zoom into. That would make navigating long web pages amazingly easy and powerful... better than any other browser. If you can't do that, then at LEAST provide an area to touch to rapidly scroll to top like iOS/Safari does with touching the status bar. Also want to add my vote for keeping the address bar at the bottom, and all the controls easy to reach with one hand on 5"-6" screens as best you can. Usability! And another vote for just keeping the "Spartan" name if you can (copyright/trademark/etc. and all).Anonymous
January 23, 2015
The January preview build is now available! Check out the details and try it out for yourself: blogs.windows.com/.../january-build-now-available-to-the-windows-insider-program We'll be deploying updated images to RemoteIE in the near future so you can test with the latest build from anywhere.Anonymous
January 23, 2015
The comment has been removedAnonymous
January 23, 2015
Please put the address bar below for Windows Phones. It was the best thing about mobile IE.Anonymous
January 23, 2015
Simpler, with less legacy plugin support, faster and better scurity....Anonymous
January 23, 2015
@EricLaw Hi Eric! We are working to enable HAR export in the network tool. Stay tuned. Regarding the network emulation question, we'll look into this for a future release. Please vote for it in our User Voice site if you haven't do so already: wpdev.uservoice.com/.../84475-f12-developer-tools Thanks!Anonymous
January 23, 2015
Where in the new build is spartan located. I can see the fast rendering engine in Internet Explorer but not find the new browser.Anonymous
January 23, 2015
The comment has been removedAnonymous
January 23, 2015
もう一つ、追記ですがよろしいでしょうか？？。 英語版以外の他の原語版のブログ記事の翻訳が遅すぎます。 あれからまた結構溜まってますよ、急いで下さい。 毎回毎回そういうように思ってました。Anonymous
January 23, 2015
Since I leave near a town with 'Spartan' in its name, there's a lot around here named Spartan-something-or-other. Hmmm, guess you can't copyright "Spartan." I just hope it does not go the way of the SkyDrive and end up getting renamed.... On another note, I'm still supporting a lot of SharePoint users who have trouble with IE11. Wonder how this new browser will support SharePoint functionality? It would be frustrating for users to have to switch between two different browsers, depending on what they're working on.Anonymous
January 23, 2015
Moving the address bar / refresh to the top of the screen on mobile devices is not an improvement. Having it at the bottom will let a user keep using their smaller phone one-handed. I get that you're trying to create a similar experience between all the devices, and that's a fine goal up to a point -- but we don't use all our devices in the same way.Anonymous
January 23, 2015
Internet Explorer Spartan sounds good actually... In my opinion, it sounds better as a version name rather than a completely different one.Anonymous
January 23, 2015
To all of the ones that write that a top address bar on mobile is a bad decision - What do you do more, scroll a page, or use the address bar? Having the address bar in a place where a user could have scrolled (thus making the user move their finger upwards in order to scroll) looks somewhat counterproductive to me... If anything, the new bottom bar should be removed, I think.Anonymous
January 23, 2015
nice and gud to seeAnonymous
January 23, 2015
if can add more demo from spartanAnonymous
January 23, 2015
@Numbstill The address bar below the page does not interfere with scrolling for me I would like it to stay belowAnonymous
January 24, 2015
to those to recommend WebKit, given the number of times mobile Safari crashes on the iPad I take it you are joking . Like the mobile IE look, I guess i'm lucky as I have two arms, but please add gestures to quickly nav to the top or bottom of a page, a refresh mostly positions itself back to where the page was and i'm normally looking to either get back to the sites main navigation or down to the comments.Anonymous
January 24, 2015
The comment has been removedAnonymous
January 24, 2015
The comment has been removedAnonymous
January 24, 2015
Microsoft must develop an Android version.Anonymous
January 24, 2015
I prefer to have the address bar at the bottom on Windows Phone and on tablets / Surface Pro. What will happen to the modern UI version of IE? actually the modern app was quite good for tablet / touch use. will the modern IE app also be available besides Spartan and desktop IE?Anonymous
January 24, 2015
The comment has been removedAnonymous
January 25, 2015
So there're two news here. A new rendering engine (probably a good thing). And a new UI. So far I feel that the UI has compromised usability. Address/search bar on top seems unfortunate. IE11 on WP had really nailed it by placing it in the bottom... I share pages much less often then I search the web/enter URLs.Anonymous
January 25, 2015
Want it now! That is all.Anonymous
January 25, 2015
Enterprise constrained: Can I keep IE 9, our corporate standard, and install and play with Spartan on my enterprise Windows 7 work station?Anonymous
January 25, 2015
@Fabio duarte If I want a page opened in antother tap i want that to be active and keep de current page in a background tab. As most people probably do.Anonymous
January 25, 2015
Could you please also unveil (e.g. in some future post), what impact this browser and rendering engine duality will have on the programmatic interfaces (IWebBrowser2 et al.)? Or shall be there some new API to embed browser in 3rd paty desktop apps?Anonymous
January 25, 2015
I Think IE Address bar search method very weak in comparison with Firefox. +without quick available website history ?Anonymous
January 26, 2015
Amazing work, I'm looking forward to the release! However, before you do so, please put the addressbar back on the bottom, where it should be. ;)Anonymous
January 26, 2015
@Tom 1/23/15 2:33 PM You should be able to add and edit styles in the DOM Explorer. The styles panel is just on the right hand side and clicking should edit and you can use a context menu to add a new item. @Domenic Denicola 1/22/15 5:59 PM Promises should be instrumented for async call stacks.Anonymous
January 26, 2015
IE dev team. First, congrats on producing a cool new browser! Second, please keep with Modern UI standards and layout. As another person said, having the address bar at the top is going to be a very hard UX for those with 1520's and other large screen Windows Phones. The buttons at the bottom (where Share is, etc.) aren't showing the correct Modern UI buttons (round with icons in middle)....please use the established Modern UI round buttons! Thanks!Anonymous
January 26, 2015
On build 9926 is this normal that when checking your recent activity on your Microsoft Account under security and privacy settings when it shows your sign-ins it shows Chrome as your web browser instead of IE ? Thank youAnonymous
January 26, 2015
The comment has been removedAnonymous
January 26, 2015
How About "WebBrowser Control" developers? I'm wonder to know about interoperability, APIs, etc. Where I can read about?Anonymous
January 26, 2015
The comment has been removedAnonymous
January 26, 2015
Make Spartan available for Windows 7 & 8.1 >> Enterprises won't upgrade their OS within years. Chrome even runs on XP!Anonymous
January 26, 2015
From the looks of it, Project Spartan is looking amazing, for those developers complaining "not yet another browser" well develop 1 for all i.e. responsive. The Spartan UI looks in keeping with the Microsoft theme and looks very user friendly, I cannot wait to get my hands on this ad test the features it will boast. As a MAC fan to date, I am almost at the point of needing to admit W10 will convert me upon final official release. Keep up the good work Team MSAnonymous
January 27, 2015
i just wanted to suggest a Name for Project, How About 'Enterprise'? masud_4b354@yahoo.comAnonymous
January 28, 2015
Will Spartan support HTA?Anonymous
January 28, 2015
Congratulation, This is looking awesomeAnonymous
January 28, 2015
The more I think about it, the more I see the layered meaning behind the name. //name/development_philosophy/mindset. And it's just cool. To borrow from Ryan Hayes, "Make it so!" Spartan, adj. a. Rigorously self-disciplined or self-restrained. b. Simple, frugal, or austere: a Spartan diet; a spartan lifestyle. c. Marked by brevity of speech; laconic. d. Courageous in the face of pain, danger, or adversity.Anonymous
January 28, 2015
I just see Halo spartan supersoldiersAnonymous
January 29, 2015
@Sergio and others who gave feedback regarding the mobile UI: We're continuing to evolve the UI and encourage you to give feedback at UserVoice! windowsphone.uservoice.com/.../6993955-keep-the-spartan-address-bar-at-the-bottom @Evgeniy OZ - You can try out the new rendering engine today in Remote IE using the Windows 10 Technical Preview. We'll continue to update the engine and add Project Spartan to Remote IE in later updates. Stay tuned!Anonymous
January 29, 2015
@arizdev We're working on some updates to our blog and other web properties in the coming months - stay tuned!Anonymous
January 29, 2015
Would be good to see a single answer to all of @EricLaw's points. From my perspective I'd love the ability to make the browser my own. Access it programmatically so that it can do what I want (rather than what some hypothetical "consumer" might want). I don't really want some sandboxed, JavaScript only, way of talking to the machine. What I want is a way to access the browser from .NET and maybe Powershell code, that integrates it with my own custom desktop tools. I know there's an overwhelming tendency to dumb the Internet down, but there's a need, for many, to treat the browser as a serious tool. We feel abandoned in the mad scramble for easy, mindless and "you have no way to do your own thing". What is going to offered in this space?Anonymous
January 29, 2015
Oh yea. The remote browser version disconnects fairly often so testing with it must be limited. Will this improve?Anonymous
January 29, 2015
Can I just go back to "Windows Memphis " now? it is what Elvis would want!Anonymous
January 29, 2015
looks good, hope it works wellAnonymous
January 29, 2015
希望ie還是能出新版本 ie真的很好用Anonymous
January 30, 2015
@EricLaw : taking advantage of the free upgrade to Windows 10, is not a decision to take lightly, as the ultimate deciding factor for me, will be based not just on my current hardware, but whether all installed software, will be compatible in Windows 10. I have spent thousands of dollars on software, and do not like the thought of having to replace said software, with newer versions (if available) to get it to run in Windows 10.Anonymous
January 31, 2015
This is a good idea... What will happen to IE?Anonymous
February 03, 2015
15 year web developer here. HTML5: Input type=number... barely works in ie. No spinners like chrome. Allows you to type letters. input type=datetime-local ... wouldn't it be nice to have a pop-up calendar, without having to use jqueryui. "required field": wouldn't it be nice if this worked with standard ajax buttons, and not only submit/command buttons. Firebug: I can't web-program anymore without using firebug in firefox. Unrelated: MVC still has no grid. I'm forced to use bootstrap datatables, or pay($1000) for Telerik, as MVC hasn't fully caught up to webforms/ajax toolkit, and certainly not Telerik, in terms of widgets. Grids with autocomplete searches that download in excel with a few lines of code. Available, just absent from Microsoft in MVC5/6.Anonymous
February 03, 2015
Microsoft Internet Explorer Universal Cross-Site Scripting Flaw(0day?) thehackernews.com/.../internet-explorer-xss.html Hurry up!!!Anonymous
February 04, 2015
The comment has been removedAnonymous
February 04, 2015
The comment has been removedAnonymous
February 04, 2015
good achievement.Anonymous
February 04, 2015
@drd - Please, use this UserVoice for user interface feature requests - windows.uservoice.com/.../87567-internet-explorerAnonymous
March 06, 2015
This look good, but can't height of address bar be more thin so there is more room for webpageAnonymous
March 16, 2015
The comment has been removedAnonymous
March 17, 2015
The comment has been removedAnonymous
March 17, 2015
Haven't used IE for years and this sure isn't showing any reason to return to using a MS browser. MS really needs to learn a PC is not a phone or tablet, so stop trying to make them all the same! While an integrated search/address bar is practical for a mobile device it was the first reason to go away from IE.Anonymous
March 18, 2015
Should change IE to IV for Voyager. It sounds great.Anonymous
March 19, 2015
Who cares? You only try because you lost the market to Chrome and Firefox. Might as well keep out and stay out.Anonymous
March 19, 2015
Well @Simon. Netscape lost their market to Internet Explorer, they change the name and their attitude and now Firefox is a great browser. Some guys, like you, even quote that now Firefox has more market than IE, incorrectly of course. If you don't like just left us alone and continue to write your prefixed code.Anonymous
March 22, 2015
Your mantra should be 'compatibility'. That's the only - emphasis only - thing you should be worried about. Get that right, and then you can start putting bells and whistles on it. IE has been an albatross on the web dev industry since forever. While you are at it - backport devtools upgrades to IE9+ too! Clean up your legacy before dropping new products, and help give your immense user base better experience by supporting developers who have to in turn support them. Thanks.Anonymous
March 29, 2015
I couldn't find spartan in windows 10 latest version .How can i find .Will i have to downloaded itAnonymous
March 30, 2015
@Muizz Spartan in its full form is not available in the current built (10041). IE team promiss they will try release it in the next build to be released next month (probably). In the current build you can just use the new Edge engine by enabling features in about:flags.Anonymous
March 31, 2015
please serial for active windows after install build 10049 tanksAnonymous
April 01, 2015
Sounds good. Just think it should be up to the user what they want on the computer. Windows 10 seems to force stuff on people without giving them the choice to uninstall things. Like I don't want to use Onedrive but I can't uninstall it. Same with IE and Spartan. Its like its forced on people. Windows Explorer seem more things that I would never use. I still like Windows 7 better than 10.Anonymous
April 03, 2015
The comment has been removedAnonymous
April 04, 2015
The comment has been removedAnonymous
April 05, 2015
Great Info, But I think it's not better than Google Chrome and Firefox as shown in the video review here techfumes.com/microsoft-project-spartanAnonymous
April 06, 2015
T4ET4ET43Anonymous
April 08, 2015
I'm assuming that built-in language translation is coming in a future build. As an international business and traveler I ended up installing Google Chrome for this feature after receiving Spartan through the Windows 10 Preview on my Surface Pro 3 while in Japan last week to get this feature. It was very cumbersome to have to go an external resource to translate a web pages' content before meeting with a client.Anonymous
April 09, 2015
I have question, i hear from Autodesk that new IE , will support opening filest from Autodesk 2D and 3D only by using browser , is that true ?Anonymous
April 14, 2015
The comment has been removed