Allow Edge to be updated on its own
Microsoft isn’t updating Edge via the Store as originally promised. Edge updates seem to be held back for major new versions of Windows 10, unlike Windows 10’s other included apps, which are updated more regularly. A good example is the big Nov 2015 Windows update which is the only way to get Edge 25 with EdgeHTML 13 including the drag & drop file fix.
As a web developer I can safely assume Firefox and Chrome users are on the latest version (we don't support the versions pre auto-update). I can't for Edge because major Windows updates are non-trivial and not always installed. Edge was supposed to end the nightmare of multiple IE versions, but in a way it's actually worse.
Please make Edge a true "evergreen" browser by allowing it to be updated separately from Windows.
Having different versions of EdgeHTML around forces development to focus on the lowest common denominator - EdgeHTML 12, or to drop support for Edge completely. Sites 'not working' in Edge pulls users back to Chrome and Firefox.
Not all Windows-users can in practice update to newer builds of Windows 10 due to quality concerns unrelated to Edge. Dear Edge team, please don't let your product fall behind in market share or fail due to problems caused in other Windows-teams, we're rooting for you!
Microsoft - Since IE 6 you're making web developers lives miserable. It's time that you align with the standards and stop lagging behind. With the advent of emscripten, asmjs and WASM, more and more products are porting C++ code, the standards are updated frequently and there's a real need for frequent browser updates. If you're looking to maintain or increase the ~8% market share, you'll have to step up. Please consider.
Tim van der Horst commented
Edge is not "Evergreen" until it can update without an OS update :(
Ferdy Christant commented
This issue is my biggest pet peeve right now. In this last year, I've finally seen the Edge team commit and pick up a lot of important issues that consist of core new web technologies with many votes. So the direction and focus overall seems positive.
The tediously slow release cycle completely evaporates this positive movement. Major releases containing these essential web tech updates are a 6 month wait, and then we still can't use the tech because we rely on customers doing these huge updates. What does that make it? A 9-12 month wait to use a feature?
Aren't you embarrassed that your very own invention "CSS grids" is launched almost together by all major browsers except Edge?
You're building the right features. Finally. But it's no use if you don't release them. Release them as early as you can, and stop the Windows update dependency. Speed up!
I've been very excited about the next major release but it's taking so long that it's like waiting for baby to be born.
Cédric Belin commented
MS Edge is an excellent browser, yet I am still obliged to regularly tell my customers: install Chrome or Firefox. In fact, nothing has changed since IE 11 was abandoned : updating the OS to get the latest version is an option that most of my customers simply can't do.
And waiting 30-40 minutes in order to get the latest version while it takes less than 5 minutes with other browsers... It's insane.
Microsoft: No plans to separate Edge browser updates from Windows 10, "but never say never" https://www.neowin.net/news/microsoft-no-plans-to-separate-edge-browser-updates-from-windows-10-but-never-say-never
Microsoft has denied the earlier rumor of Edge heading to the store.
My company is still running on Win 10 RTM.
Not being able to upgrade Edge makes web dev a nightmare as I have to do everything in VMs with more recent Win 10 releases.
"...according to a new report from Neowin.net, sourced from insiders, Microsoft will be addressing this in the September Redstone 3 Windows 10 update. The app is heading to the store, and this would allow Microsoft to make as many updates as needed to the Edge browser to make it more competitive, an approach we saw working to great effect with the Groove music client, though of course there are no guarantees this will indeed be the case.
Of course, many apps rely on the stability of the Edge rendering engine, and Microsoft has said last year that even though they may update the browser independently, they are still likely to save rendering engine updates for major versions."
Claude Pache commented
“As a web developer I can safely assume Firefox and Chrome users are on the latest version...” Uh, as a web developer, I surely know that a significant proportion of Firefox and Chrome installations are out-of-date, even some of them are obsolete for more than a year.
Matthias Kurz commented
"... but the engine of Edge will always be updated with Windows Update."
So does this mean also in future the EdgeHTML engine will be updated like only once or twice per year? This sucks. Compare this to the six weeks release cycle that Firefox and Chrome follow.
"... states that Edge app, which includes navigation controls, reading view and other similar features will eventually get updated through the store but the engine of Edge will always be updated with Windows Update."
100% needs to be updated outside of the OS - I don't care if it's updated in Windows Update or Store Update, but it needs to be independent of the OS. My company is on 1511 and will be for 12+ months because of the required SCCM upgrades to support 1607+, so we are stuck on OEM 1511 Edge 13... just like we are stuck on IE 11... no wonder why all my users just want Chrome.
meant to say "edge versions*" and "force updates" as in background updates so the end user doesn't need to know. And I would say this common experience should be updated monthly or so, even if this month only :placeholder-shown was added etc.
Please make the version of Rendering in Edge irrelevant. Do this by updating the rendering engine to a common engine across all edge version, and force updates if the user connects to the internet.
Would be nice to get a comment from Microsoft on this issue, as it is pretty crucial to modern development. Otherwise it seems like the post-IE era is pretty similar to the regular IE area.
Paul Thurrott: Microsoft, It’s Time to Treat Edge Like a Real App
"Because Microsoft’s new Edge web browser is stuck on the Windows 10 upgrade schedule, it has been updated infrequently in the past year, and it still lags behind the competition. Microsoft, it’s time to fix this problem and make Edge an app. And then just update the **** out of it going forward."
+1. please quicken the release cycle.
Edge is not tied to the OS, but is a choise to align major platform updates to the Windows release cadence, as you can read in a comment of a Program Manager of Edge under this blog post: https://blogs.windows.com/msedgedev/2015/11/16/introducing-edgehtml-13-our-first-platform-update-for-microsoft-edge/
Grzegorz Wiktorowski commented
As far I understand Microsoft Edge is in WUA technology the same as Weather, Mail, Finance, Sport and Maps apps They are updated in the month cycle. It seems Edge is so deeply tied up to OS that the story looks similar to IE. There are too many quirks in Edge so waiting 6-7 months for the release is unacceptable.
I believe it's important that Microsoft Edge can be updated separately from the OS, as otherwise those who are having difficulties updating to a newer Windows 10 build don't hold back web developers overtime. Also, small security or feature additions to Microsoft Edge aren't trivial if a whole new OS build needs to be installed to be able to take advantage of them.