Meet the browser: Microsoft Edge Next


Recommended Posts

George P

Anyone check out Edge in the newest 14366 insider build?  I know there's that new Office Online extension for it, anything else?

  • Like 1
Link to post
Share on other sites
margrave

I'm not using Edge until I can drag from the address bar to make a shortcut/link, and also drag links/shortcuts into the browser to open them.

Link to post
Share on other sites
BooBerry
6 hours ago, George P said:

Anyone check out Edge in the newest 14366 insider build?  I know there's that new Office Online extension for it, anything else?

Quote

Performance and security matter to everyone. Better page load performance improves the user’s experience and influences their choice over which web pages to use. At the same time, users just expect their browsing experience to be secure and private. With TCP Fast Open, TLS False Start, and TLS 1.3, we can improve both performance and security.

Today, we’re introducing support for TCP Fast Open in Microsoft Edge behind an about:flags setting in Windows Insider Preview builds, starting with EdgeHTML 14.14361 and higher. Try it out and let us know what you think!

The road to TLS 1.3

We trust the internet with our most important information, including financial data.  Ensuring the integrity and security of these transactions is critical to the entire community.  More than half of web connections use TLS for securing the network traffic on the web, and this number grows every day. This is great for security and privacy, but we would like to deploy encryption without slowing down the web. Modern encryption itself is very fast, but requires negotiating keys to establish a connection before fetching page resources.  Each extra exchange through the network delays the connection by one “round trip time” (RTT).

With current standards, connections requiring TLS over TCP require round trips to the server (3-RTT) to negotiate—1 for TCP and 2 for TLS—before starting sending something useful, like the first HTTP GET command. This gets even more problematic when sites split content across multiple domains.  In practice, adding encryption adds delays in the range of hundreds of milliseconds to the page load time. Research shows that even 250ms delay is enough for a user to consider trying another website.

The good news is that a new standard, TLS 1.3, will allow developers to eliminate that delay in most cases while still encrypting content. That means delivering better performance and security in Microsoft Edge, using modern encryption on top of the continually improved TCP stack. TLS 1.3 is working through the standardization track now, and the IETF expects to publish it this summer. But even without TLS 1.3, we can combine TCP Fast Open and the TLS False Start option, and reduce the delay from 3-RTT to 1-RTT. Even reducing your page load time by an average of 50 milliseconds will contribute to a better browsing experience.

Full handshake with TCP and TLS

The current TCP and TLS standards require 3 roundtrips to the server (3-RTT).  The first round trip is where we negotiate the TCP connection parameters. In the second roundtrip, the client and server exchange TLS messages starting with Client Hello and Server Hello to agree on parameters and keys of the connection. The last roundtrip includes the verification of the TLS handshake integrity through the Client and Server Finished messages.

Diagram illustrating a full handshake with TLS, requiring three roundtrips.

Full Handshake – TLS 1.0, 1.1, 1.2

Achieving 1-RTT with TLS False Start and TCP Fast Open

The first improvement comes from the TLS False Start option, which allows the client to start sending encrypted data immediately after the first TLS roundtrip. With that, we are down to 1-RTT for TLS, or 2-RTT if we count the TCP connection. We have already enabled TLS False Start in Microsoft Edge, with a set of strong cipher suites.

Diagram illustrating an improved handshake with TLS False Start, which reduces the roundtrip time to 2-RTTs.

TLS False Start – TLS 1.0, 1.1, 1.2

The next improvement comes from the TCP Fast Open procedure, defined in RFC 7413. The RFC defines a new TCP option, containing a “Fast Open Cookie.” When a “Fast Open capable” client connects to a server for the first time, it inserts an empty cookie in the initial TCP SYN message, prompting the server to send back a valid cookie in the response. For the subsequent connections, the client copies the cookie in the TCP SYN message, and then sends data immediately. If the server recognizes the data as valid, it will accept the data and pass them to the application. When TCP Fast Open is enabled, data can be sent before the connection complete, and the responses will arrive immediately. When we combine TCP Fast Open and TLS False Start, the key negotiation is performed simultaneously with the initial TCP handshake. There is just 1-RTT before the HTTP traffic starts.

Diagram illustrating the combination of TCP Fase Open and TLS False Start, which allows the key negotiation to be performed simultaneously with the TCP handshake, resulting in just 1-RTT.

TLS False Start with TCP Fast Open

What’s next: 0-RTT with TLS 1.3

TCP Fast Open is available behind an about:flags setting in Microsoft Edge in Windows Insider Preview builds 14352 and higher. You can manage the TCP Fast Open setting by navigating to about:flags in the address bar. TCP Fast Open is currently off by default in Microsoft Edge for “HTTPS” connections, but we may adjust this in future preview builds in order to get more telemetry data.

Screen capture showing the TCP Fast Open toggle under "Networking" in about:flags.

TCP Fast Open can be managed via about:flags in Microsoft Edge

The next stage in our journey is to move from 1-RTT to 0-RTT using TLS 1.3. It turns out that doing 0-RTT safely is quite tricky—all 0-RTT solutions require sending key material and encrypted data from the client without waiting for any feedback from the sender. At a minimum, that means that adversaries can capture and replay the messages, which implies that the feature has to be used with great care. In addition to that, there are many potential pitfalls, such as compromising privacy by carrying identifiers in clear text in the Hello message, or risking future compromise if the initial encryption depends on a server public key. The IETF working group is working through these issues now, and as they are resolved we expect to see adoption calls this summer and publication of the standard a few months later.

Diagram showing TLS 1.3 Session Resume combined with TCP Fast Open for 0-RTT handshakes.

TLS 1.3 Session Resume combined with TCP Fast Open

We know performance and security matter to our users and we’re committed to delivering a 0-RTT experience in Microsoft Edge through HTTP 2.0, TLS 1.3, TCP Fast Open, and TLS False Start. We’re also going to continue to work with industry leaders and experts in the standards bodies to build an interoperable TLS 1.3 solution for the web. You can try TCP Fast Open and TLS False Start on Windows Insider Preview builds today

 

  • Like 8
Link to post
Share on other sites
  • 1 month later...
  • 1 month later...
Boo Berry

This is likely why uBlock Origin isn't visible on the Windows Store yet.

Link to post
Share on other sites
  • 1 year later...
George P

This topic hasn't been updated in quite some time it seems, shame really as I use Edge along with Vivaldi on my systems.  The newest version, 42.17134.1.0 that comes with the April 2018 update is a very nice improvement over the one before.  Still, the only issue I keep having, at least on my desktop, doesn't happen on my laptop though, is on the front page of Neowin.  If I go into a FP post with lots of comments and try to replay the page UI will lock up, can't scroll up or down.   Edge itself keeps working fine, I'm just forced to reload the page.   Only on posts with 20-30+ comments, when it's only a handful it doesn't happen.  Also it doesn't happen on my laptop, but that could also be because I don't open anywhere near the number of tabs on that compared to my desktop, so that could come into play.

Link to post
Share on other sites
+Zlip792
17 hours ago, George P said:

This topic hasn't been updated in quite some time it seems, shame really as I use Edge along with Vivaldi on my systems.  The newest version, 42.17134.1.0 that comes with the April 2018 update is a very nice improvement over the one before.  Still, the only issue I keep having, at least on my desktop, doesn't happen on my laptop though, is on the front page of Neowin.  If I go into a FP post with lots of comments and try to replay the page UI will lock up, can't scroll up or down.   Edge itself keeps working fine, I'm just forced to reload the page.   Only on posts with 20-30+ comments, when it's only a handful it doesn't happen.  Also it doesn't happen on my laptop, but that could also be because I don't open anywhere near the number of tabs on that compared to my desktop, so that could come into play.

This issue was already discussed somewhere on this forum or else.

 

It is due to adblocking extension in Edge. I would recommend that you try after disable and try it.

Link to post
Share on other sites
George P
2 hours ago, Zlip792 said:

This issue was already discussed somewhere on this forum or else.

 

It is due to adblocking extension in Edge. I would recommend that you try after disable and try it.

That's what I thought as well, but I only have lastpass installed.   Maybe after the uninstall I'll have to restart edge though, which I didn't do yet, and see how it goes.

Link to post
Share on other sites
George P

Ok, just tried after a restart, no adblockers installed, still locks up for me.  Just weird I guess.

Link to post
Share on other sites
+Zlip792
42 minutes ago, George P said:

That's what I thought as well, but I only have lastpass installed.   Maybe after the uninstall I'll have to restart edge though, which I didn't do yet, and see how it goes.

Can you check, which about:flags are enabled?

 

Further, you can unlock more settings in the about:flags by pressing "Ctrl+Shift+D" and ensure that it is configured to 'Release'. For testing, try with 'Canary' as well.

 

Link - https://www.askvg.com/windows-10-tip-enable-hidden-diagnostics-options-on-about-flags-page-in-microsoft-edge/

Link to post
Share on other sites
George P
16 minutes ago, Zlip792 said:

Can you check, which about:flags are enabled?

 

Further, you can unlock more settings in the about:flags by pressing "Ctrl+Shift+D" and ensure that it is configured to 'Release'. For testing, try with 'Canary' as well.

 

Link - https://www.askvg.com/windows-10-tip-enable-hidden-diagnostics-options-on-about-flags-page-in-microsoft-edge/

Ok, let me check those and list them, or at least compare them to the settings in Edge on my laptop which doesn't seem to have this issue.  I'll report back.

Link to post
Share on other sites
+Zlip792
6 minutes ago, George P said:

Ok, let me check those and list them, or at least compare them to the settings in Edge on my laptop which doesn't seem to have this issue.  I'll report back.

Further, can you give me following information?

 

- Front Page reproducible link?

- Antivirus (if different on both - whether HTTPS inspection is enabled or not)

- Addons on both?

- GPU and driver version?

 

Most probable culprit from my perspective could be GPU or HTTPS inspection. If you share the link, I will try to reproduce on my work laptop and see. (Don't have access to any other system - since I am out for project in another country since August 2017). ??

Link to post
Share on other sites
George P
2 minutes ago, Zlip792 said:

Further, can you give me following information?

 

- Front Page reproducible link?

- Antivirus (if different on both - whether HTTPS inspection is enabled or not)

- Addons on both?

- GPU and driver version?

 

Most probable culprit from my perspective could be GPU or HTTPS inspection. If you share the link, I will try to reproduce on my work laptop and see. (Don't have access to any other system - since I am out for project in another country since August 2017). ??

Ok, I figured out what the issue is exactly and it might be a bug specific to neowin because I haven't had this happen on other sites.   On my desktop I use a default zoom level of 150%, helps me with reading text, on neowin if I use a lower zoom level, like the default 100% or 125%, no front page lock, page works fine.  Once I raise it to 150% and try to reply to a post on FP, it'll lock.  So maybe it's the zooming/scaling side + my older gfx drivers?   I figure for now I can just reduce the zoom level to 125% on the front page if I have to to work around it.

Link to post
Share on other sites
+Zlip792
1 hour ago, George P said:

Ok, I figured out what the issue is exactly and it might be a bug specific to neowin because I haven't had this happen on other sites.   On my desktop I use a default zoom level of 150%, helps me with reading text, on neowin if I use a lower zoom level, like the default 100% or 125%, no front page lock, page works fine.  Once I raise it to 150% and try to reply to a post on FP, it'll lock.  So maybe it's the zooming/scaling side + my older gfx drivers?   I figure for now I can just reduce the zoom level to 125% on the front page if I have to to work around it.

It is more likely related to Edge - Paint or Layout performance issue + Old GFX driver issue.

 

I will recommend you to update the GFX drivers to get smooth experience and optimal performance.

Link to post
Share on other sites
George P
4 minutes ago, Zlip792 said:

It is more likely related to Edge - Paint or Layout performance issue + Old GFX driver issue.

 

I will recommend you to update the GFX drivers to get smooth experience and optimal performance.

Yeah, I'll upgrade drivers and see how it goes.  Thanks for helping out. 

Link to post
Share on other sites
  • 11 months later...
George P

So since the new chromium based Edge is still Edge I suppose we don't need a whole new topic for it.  

 

Anyways, I'm on Canary and the version was just bumped up to 75.0.124.0 for those who are keeping track.

Link to post
Share on other sites
  • 3 weeks later...
Chicane-UK

Been using the dev Edge for a week or two now and am actually really pleased with it.. seems very fast and free of "cruft". To be honest if I could have imagined a perfect browser it would have been Chrome based but without all of Google's bolt-in's so I guess it's perfect for me. Also rather awesome that it'll be coming to macOS as I use that too so... will be able to keep both browsers sync'd up in terms of bookmarks, settings, etc :)

  • Like 1
Link to post
Share on other sites
Brandon H

I hope they change their mind on Linux support at some point as I still say that's a huge missed opportunity. If they don't want to upkeep multiple Linux repositories they could package it as a SNAP app or something.

  • Like 1
Link to post
Share on other sites
George P
3 hours ago, Brandon H said:

I hope they change their mind on Linux support at some point as I still say that's a huge missed opportunity. If they don't want to upkeep multiple Linux repositories they could package it as a SNAP app or something.

Have they officially said no Linux version ever?  Or just that it's not in the plan right now?  Because I can see them releasing one later, maybe going off of the macOS version which is probably a good starting point code wise compared to the Windows version.   They'll have to add more features before they should expand it to more platforms.

 

Speaking of which, anyone on the newest Canary build?  76.0.141.0?   My youtube kb controls are borked with this version it seems.  I used to be able to use the arrow keys for volume and skip forward, back.  Now volume works, sometimes, but hitting the right arrow doesn't skip the video ahead anymore.  It's so annoying right now.

 

*edit* Well, heck, right after I posted this I checked for a newer build and am now on 76.0.144.0 and it's working again.  

Link to post
Share on other sites
Brandon H
8 minutes ago, George P said:

Have they officially said no Linux version ever? 

not specifically but announced support is only as follows:

 

WIndows 7/8.1/10

MacOS - coming soon

 

and Android/iOS mobile apps are being updated to make syncing compatible but not much else at this time

Link to post
Share on other sites
Chicane-UK
6 hours ago, Brandon H said:

I hope they change their mind on Linux support at some point as I still say that's a huge missed opportunity. If they don't want to upkeep multiple Linux repositories they could package it as a SNAP app or something.

 

Agreed... it'd be pretty awesome on Linux. They're already doing other products for Linux (e.g. Visual Studio Code) - doesn't seem like a browser based on something already available on Linux would be such a massive stretch. 

Link to post
Share on other sites
George P

There are some reports that the newest canary build has working spell check for some.  It's still not working for me, anyone have it working for them?

Link to post
Share on other sites
PsYcHoKiLLa
14 hours ago, George P said:

Have they officially said no Linux version ever?  Or just that it's not in the plan right now?  Because I can see them releasing one later, maybe going off of the macOS version which is probably a good starting point code wise compared to the Windows version.   They'll have to add more features before they should expand it to more platforms.

 

Speaking of which, anyone on the newest Canary build?  76.0.141.0?   My youtube kb controls are borked with this version it seems.  I used to be able to use the arrow keys for volume and skip forward, back.  Now volume works, sometimes, but hitting the right arrow doesn't skip the video ahead anymore.  It's so annoying right now.

 

*edit* Well, heck, right after I posted this I checked for a newer build and am now on 76.0.144.0 and it's working again.  

 

Yeah I noticed the cursor keys issue too, reported it using the tool. On mine, pressing the cursor keys throws the cursor into the address bar, especially annoying when you are navigating a comment you are creating and forget.

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    No registered users viewing this page.

  • Similar Content

    • By Abhay V
      A near-final build of Windows 10X has leaked to the web
      by Abhay Venkatesh



      A near-final build of Windows 10X has leaked on to the web, giving those interested in going through the tricky process of installing it a glimpse at Microsoft’s latest OS – a competitor to Google’s lightweight Chrome OS. The initial release is expected to be aimed only at single screened PCs and is reportedly set to launch this spring.

      Windows 10X was first showed off back in October 2019 and was aimed at dual-screened devices like the Surface Neo. However, with the Neo delayed indefinitely, the Redmond giant repurposed the OS for single-screened devices. Additionally, while the OS was expected to debut with support for Win32 apps through a virtualization technology called VAIL, those plans reportedly changed, making Windows 10X an offering slated to debut on low-end devices due to its lightweight nature.

      Microsoft is supposedly planning to add Win32 app support in the future and the OS is not expected to arrive on new form factors – such as dual-screened devices – till at least 2022. A report from The Verge suggests that the leaked build contains support for Win32 apps in a developer-only mode which cannot be accessed by general users. For now, the offering runs UWP apps from the Microsoft Store and Progressive Web Apps through the Chromium-based Edge browser.

      With the development of the company’s lightweight OS now nearing completion, it will be interesting to see when the firm plans to unveil the offering officially. Rumors are making the rounds that the launch will be one without much fanfare. OEM partners are also expected to unveil low-power PCs running Windows 10X aimed at the education market and the like in the coming months.

      Considering the risks and complexities associated with installing leaked builds, we will not be posting links to any resources for the build. Additionally, we always urge users to exercise caution and not install these builds on their main machines.

    • By Abhay V
      Microsoft releases Edge Dev 89.0.760.0 with Password Monitor for Mac users
      by Abhay Venkatesh



      Microsoft has released the second Edge Dev build for this year, bringing version 89.0.760.0 to users in the Dev channel. Today’s build adds a few new features, chief of which is the Password Monitor feature for macOS users. While the feature has been available to Insiders on Windows for a while now, it is being enabled for Mac users with this build. As a reminder, the firm added support for Apple Silicon Macs with last week’s build.

      In addition to the password monitor, there are a few other minor additions relating to management and update policies. Here is the complete list of features added with today’s release:

      As usual, the update also brings with it a bunch of reliability improvements. Here is the complete list of fixes:

      And here are all the fixes for changed behavior:

      Lastly, there are a bunch of known issues with the update, some of which are being tracked for a past few releases. Here are all the known issues:

      The browser should automatically be updated in the background for Dev users. However, you can also force-check for an update via Settings > About Microsoft Edge and pull the update manually.

    • By Rich Woods
      Edge Dev 89.0.752.1 is out with support for Apple M1 chips
      by Rich Woods



      It's been a few weeks due to the holiday season, but Microsoft released a new Edge Dev build today. It brings the browser to version 89.0.752.1, and the most notable new feature is that it supports Apple's new ARM-based MacBooks. The feature showed up in the Canary channel in mid-December, but Microsoft paused all updates through the holidays.

      As for what else is new, it's mostly minor features. Here's the full list:

      And of course there are a bunch of fixed and known issues. Here's what got fixed for improved reliability:

      Here are the fixes for changed behavior:

      Finally, here's the list of known issues:

      You can manually update your browser by going to Settings -> About Microsoft Edge. If you don't feel like it, you can just wait for it to update in the background.

    • By Abhay V
      Microsoft begins rolling out history and open tabs' sync for users on Edge stable
      by Abhay Venkatesh



      Microsoft made its Chromium-based Edge browser generally available back in January last year. The rollout was a slow one and the company did not begin shipping the browser with Windows 10 till the October 2020 Update (version 20H2). However, one significant feature that was absent at launch – and one that is still not completely available – is the ability to sync browser history and tabs across devices. The feature began rolling out to testers in October and has been a long time coming.

      Now, it looks like users running the stable version of the Edge browser have begun receiving the feature. The 'History' and 'Open tabs' options under the ‘Sync’ page in settings are now being enabled for some users, and it looks to be a server-side change. Enabling the feature lets users sync their browser history across devices, making it easy to pick up where they left off, not just on Windows PCs but also across other platforms such as macOS.

      The feature also began showing up for a small set of users on Android devices last month. With the rollout now commencing – albeit in a limited manner, it will not be surprising to see the capability make it to the mobile versions of the browser for all users soon. The addition of the feature will also make it easier for more users to switch to Edge from competing offerings such as Chrome.

      Are you able to enable history and tab sync on your Edge browser? Let us know in the comments!

    • By Rich Woods
      Motorola announces 23 phones getting Android 11, showing how convoluted its lineup is
      by Rich Woods

      Today, Motorola announced a long list of phones that it plans to update to the latest version of Android, Android 11. In its entirety, there are 23 smartphones on the list, ranging from the firm's latest razr and edge flagships, to its moto g and one mid-range devices. None of the moto e entry-level devices are getting an upgrade.

      Here's the full list, including one Lenovo-branded smartphone:

      You'll notice that while 23 devices sounds like a lot, it's not actually because Motorola is expanding its support to older or lower-end devices. No, it's just a reflection of how large and confusing the company's lineup has become. There are now 12 moto g devices that fall under the two-year support umbrella, and then another six Motorola one devices that are in the same mid-range category. That makes up for over three quarters of the list.

      And then you have the two razr and two edge handsets, which make up the flagship segment. One line of devices to not make the list is moto z, so we can probably assume that the moto z line is dead (we've reached out to Motorola for confirmation). The moto z line was introduced as a replacement for the moto z in the flagship segment, offering modular attachments. Over the years, the devices became less premium in an attempt to lower the cost of the device itself and therefore lower the cost of the package of the phone and some moto mods.

      Motorola didn't say when these devices will get their Android 11 updates, but they'll likely arrive throughout 2021.