Nov 17 2020 11:00 AM
Hello Insiders! Today we’re releasing build 88.0.702.0 to the Dev channel. It’s a big one, so we’ve got a lot to talk about:
As for all the good stuff in this build:
Added features:
Improved reliability:
Changed behavior:
Known issues:
Next week is the Thanksgiving holiday for us in the United States, which means that there will be no major Dev update, no intended minor Dev, Beta, or Stable updates, and Canary will only be updated on Monday, Tuesday, and Wednesday. We’ll be back to normal the week after!
Nov 17 2020 11:42 AM
Nov 17 2020 12:03 PM
Thanks for the update,
I wanted to ask you something about history sync.
will history sync make Edge web history appear in Windows 10 timeline/taskview, just like Edge legacy?
Nov 17 2020 01:09 PM
Nov 17 2020 08:19 PM
@josh_bodner Rubber banding is not reproducible most of the times. I am seeing this from many months. Now with newly introduced history panel rubber banding only happens half of the time. Very hit and miss, I like the effect but getting it only sometimes makes for an inconsistent user experience.
Nov 17 2020 08:45 PM
@josh_bodner seems full page web capture is not rendering the image as expected, see example screenshot where top menu banner is showing in the middle of the page rather at the top of the page?
Nov 17 2020 10:15 PM
Thanks for the update.
When will the iOS version support the synchronization of history and open tabs?
Nov 18 2020 12:17 AM
@josh_bodner Is the update not available for Linux? I can't see it in the repository.
Nov 18 2020 12:37 AM
@josh_bodner |
Love the rapid development of Edge, so much has happened since the first beta! 🙂
About automatic deduplication, will that translate back to the mobile versions as well soon?
I have Edge on my phone and tablet, and on both versions it's a mess of doubled folders and favs.
Already uninstalled Edge on both devices a couple of times to get rid of the clutter.
Other than that, loving Edge on Windows, Android & Linux!! 🙂
Nov 18 2020 01:03 AM
@DavidGB Having that behavior in the favorites menu actually gives us a lot more bargaining power that the favorites bar should behave the same, so let me ask the owner.
Nov 18 2020 01:11 AM
@kanumurikrishna Looks like we originally fixed this when you select only part of the web page, but not for the full page since that was before the full page capability was released. I'll let the person who fixed the original bug know!
Nov 18 2020 01:15 AM
@donmez I can ask, but just so I know, which repository are you looking at?
Nov 18 2020 01:16 AM
Nov 18 2020 01:17 AM
@RobWuijster Our mobile builds likely won't get this particular work for a while, although they should at least partially benefit from desktop Edge doing deduplication for them if they're syncing with builds of it that have it.
Nov 18 2020 07:04 AM
@josh_bodner The .deb linux build for this version looks to be missing from https://packages.microsoft.com/repos/edge/pool/main/m/microsoft-edge-dev/
Nov 18 2020 08:48 PM
@benbmitchell and @donmez it looks like we've had an outage that's affecting our Linux publishing, so it's known that these packages are missing and we're working on it!
Nov 18 2020 08:50 PM
@DavidGB Apparently completely unrelated to my asking, we actually just fixed this in today's Canary! The flyouts don't use the tree view yet, but the non-closing behavior will be coming to our next Dev update.
Nov 19 2020 12:19 AM
@josh_bodner This seems to be fixed now (at least rpm repos), thank you!
Nov 19 2020 04:29 AM
I am posting here so you can see it and will post to feedback, your new DEV version quit reading external reader / CAC Cards, Hence signing into CAC related sites failed with error "ERR_SSL_CLIENT_AUTH_CERT_NEEDED", Now I am unsure if that is because it might a "chrome engine" update that does it, But whatever as soon as this update hit, Sign in's failed to obtain CAC card credentials.
Nov 19 2020 05:23 AM - edited Nov 19 2020 05:34 AM
How can we know the default value of these, without guessing or trial & error?
the scrolling flags usually have little effect that are hard to notice, without knowing their default value, it's even harder to know where and how to look for changes.
of course there are other flags too that need to have their default values specified. simply saying "default" is useless.