Forum Discussion
Dev channel update to 89.0.774.4 is live
Hello Insiders! Today we’re releasing build 89.0.774.4 to the Dev channel. This is the last build for version 89, and is what we plan on shipping to Beta next week, give or take a couple of small u...
I agree opening history flyouts takes 3-4 seconds.
the favorites flyout on the other hand got so much faster, at least on Edge stable.
I have a suggestion to make History flyout open faster too. so i observed that if history sync is off, history flyout opens in less than 1 second, so the delay is caused by the sync and probably by the fact that history flyout is checking for latest history entries before showing it to the user.
i think history flyout should open quickly in less than 1 second before checking for new entries, it shouldn't keep user waiting, staring at a blank flyout.
and once it's open, then quickly check if there is any updates. and for doing that it should use a large portion of user's Internet bandwidth to do this task as fast as it can.
the favorites flyout on the other hand got so much faster, at least on Edge stable.
I have a suggestion to make History flyout open faster too. so i observed that if history sync is off, history flyout opens in less than 1 second, so the delay is caused by the sync and probably by the fact that history flyout is checking for latest history entries before showing it to the user.
i think history flyout should open quickly in less than 1 second before checking for new entries, it shouldn't keep user waiting, staring at a blank flyout.
and once it's open, then quickly check if there is any updates. and for doing that it should use a large portion of user's Internet bandwidth to do this task as fast as it can.
HotCakeX I don't believe this is limited to the History flyout. The entire app is sluggish and slow. Tab transitions (switching or opening a new one), general opening the app and viewing the default tab screen (Informational View for me), opening settings, collections, etc. are all slow in this dev release. I happen to be running this on a Surface Pro 7 Core i7, and Win10 Dev Channel 21301 build. Edge didn't have this issue prior to these two builds.