Jan 08 2020 10:39 AM
Welcome to the new year! Today we’re releasing build 81.0.381.0 to the Dev Channel, which as you can see is the first new build from major version 81. We haven’t been completely asleep during the holidays though; we’ve been slowing turning favorites sync back on for most Canary and Dev users, with the last of them coming back online a couple of days ago. As sync is re-enabled, some machines may experience duplication-like behavior as the machines get back into a clean state, but that behavior shouldn’t persist, and any changes you make to your favorites should now sync properly (but please let us know if that’s not the case!)
We also have a couple of informational updates. First, we’ve proposed our security baseline configuration for when organizations install the Stable channel of Edge: https://blogs.windows.com/msedgedev/2019/12/18/security-baseline-draft-edge-79/. There’s an accompanying discussion over on the Security Baselines forum. Second, we started a discussion around the value proposition of Reading List and how users would like to see us evolve it moving forward: https://techcommunity.microsoft.com/t5/discussions/reading-list-discussion/m-p/1070553. As for the most noteworthy product changes:
Added features:
Improved reliability:
Changed behavior:
Known issues:
We’re looking forward to the release of the Stable channel soon, and thank you for all the help you’ve given us in getting to that point!
Jan 13 2020 10:23 AM
@Deleted @Sansaido
Sure send me a PM with which Username you would like.
It has to be between 5 - 20 characters long, start with letters and have no symbols except for underscore (_) or hyphen (-).
Speak soon.
Jan 13 2020 10:38 AM
This is unbelievable lol
I just tested Dev channel on a brand new Windows 10 installation (Windows Sandbox)
Version 81.0.381.0 (Official build) dev (64-bit)
here is the result:
Jan 13 2020 12:30 PM
@ikjadoon
Pinned icons changing from specific to Edge when pinned to taskbar affects sites converted to apps. It does not apply to sites Pinned to taskbar via More tools & NOT converted to apps. I have just tested ALL 3 current Channels (again) and can confirm the bug, the behavior IS, still, happening in all 3. You are correct.
Cheers,
Drew
Jan 13 2020 01:10 PM
Jan 13 2020 04:39 PM - edited Jan 13 2020 04:42 PM
A bug does not need to hit 100% of the users to be a bug. I appreciate the follow-up troubleshooting here.
1. It was written that "it's not happening in Canary" when it can be reproduced on Canary. It's more precise (and helpful) to say, "Not happening on my Canary build with these steps."
2. It was claimed that dev users they just "need to wait", as the bug was "fixed" in Canary. That's not accurate.
3. True: as I wrote in that same first post, the taskbar icons can be cached.
4. ...again, if it's been cached, then the bug doesn't reproduce.
5. ...again, it could be cached or it could be Twitter's PWA (Twitter logged out doesn't present as a PWA on Dev; on Canary, even the logged-out state is recognized as a PWA).
Canary 81.0.392.0 is, by far, even buggier in installing apps. Some of the time, Edge Canary 81.0.392.0 won't even create the app (i.e., the menu button does nothing), takes ~20 to 30 seconds to create the app, and/or doesn't even use the favicon correctly after installing (not even pinned and it's got the wrong icon).
This bug is best reproduced on sites you've never tried to install as an app before, non-PWAs, pinning immediately after creation as an "app", and: those might not be all the conditions, but they are some. Even I can make the Google.com favicon cache on my Dev build (81.0.381.0), if I either let the window stay open for a long enough time before attempting to pin or keep uninstalling/reinstalling the site:
This bug does have corner cases where it works and where it doesn't work. But, the bug exists (on all 3x systems I own on Dev 81.0.381 + 2x systems on Canary 81.0.392.0 + 1x systems on Canary 81.0.389.0). The Canary builds are only on two of the systems and I only could test one with yesterday's Canary build, as the other had already updated.
I also created new profiles on each and the bug remains. Because of the unusual retention of whatever icon Edge wants (the correct favicon or the wrong default), as I stated in my initial post, it looks like a caching problem.
//
Again, yes: this is not a bug with "Pin site to taskbar", which simply creates a browser shortcut. "Installing" a site as an app removes the browser UI ("chrome") & forces it to always launch in a new window.
Jan 13 2020 05:09 PM
Jan 14 2020 02:02 AM
@ikjadoon wrote:
A bug does not need to hit 100% of the users to be a bug. I appreciate the follow-up troubleshooting here.
1. It was written that "it's not happening in Canary" when it can be reproduced on Canary. It's more precise (and helpful) to say, "Not happening on my Canary build with these steps."
2. It was claimed that dev users they just "need to wait", as the bug was "fixed" in Canary. That's not accurate.
3. True: as I wrote in that same first post, the taskbar icons can be cached.
4. ...again, if it's been cached, then the bug doesn't reproduce.
5. ...again, it could be cached or it could be Twitter's PWA (Twitter logged out doesn't present as a PWA on Dev; on Canary, even the logged-out state is recognized as a PWA).
Canary 81.0.392.0 is, by far, even buggier in installing apps. Some of the time, Edge Canary 81.0.392.0 won't even create the app (i.e., the menu button does nothing), takes ~20 to 30 seconds to create the app, and/or doesn't even use the favicon correctly after installing (not even pinned and it's got the wrong icon).
This bug is best reproduced on sites you've never tried to install as an app before, non-PWAs, pinning immediately after creation as an "app", and: those might not be all the conditions, but they are some. Even I can make the Google.com favicon cache on my Dev build (81.0.381.0), if I either let the window stay open for a long enough time before attempting to pin or keep uninstalling/reinstalling the site:
This bug does have corner cases where it works and where it doesn't work. But, the bug exists (on all 3x systems I own on Dev 81.0.381 + 2x systems on Canary 81.0.392.0 + 1x systems on Canary 81.0.389.0). The Canary builds are only on two of the systems and I only could test one with yesterday's Canary build, as the other had already updated.
I also created new profiles on each and the bug remains. Because of the unusual retention of whatever icon Edge wants (the correct favicon or the wrong default), as I stated in my initial post, it looks like a caching problem.
//
Again, yes: this is not a bug with "Pin site to taskbar", which simply creates a browser shortcut. "Installing" a site as an app removes the browser UI ("chrome") & forces it to always launch in a new window.
The bug is best reproduced on a fresh Windows 10 installation and that's exactly what i did by doing the test on Edge dev and it wasn't happening as you could see.
on a fresh Windows 10 installation, where no user modification has applied, it doesn't matter whether 100% users experience it or not, it won't be relevant anymore, because we eliminate the unique user configurations factor entirely.
Jan 14 2020 02:04 AM
@Drew1903 wrote:
We have always known, as well, it has oft been mentioned about not simultaneous; It is nothing new or weird, features or bugs not hitting all Users or devices nor necessarily at once. No reason this would be any different. It's almost a norm.
It keeps being repeated: The behavior, only what's converted to apps and manifesting itself in all 3 Channels. No real need for repeating these 'knowns'. Plus, we can see it happen. Can't argue reality.
I'm sure they will have it rectified, soon.
Cheers,
Drew
Sent from Windows Mobile
on a fresh Windows 10 installation, without any user configurations or even sign ins, everyone has the same experience.
Why? because there is only 1 official Windows 10 installation media.
Sent from Android Mobile
Jan 14 2020 06:45 AM
I'm also having an issue with Dev and Canary. I get access violation.
Description
Faulting Application Path: C:\Program Files (x86)\Microsoft\Edge Dev\Application\msedge.exe
Problem signature
Problem Event Name: BEX64
Application Name: msedge.exe
Application Version: 81.0.381.0
Application Timestamp: 5e0eac60
Fault Module Name: StackHash_f5c3
Fault Module Version: 0.0.0.0
Fault Module Timestamp: 00000000
Exception Offset: PCH_FD_FROM_unknown+0x0000000000000000
Exception Code: c0000005
Exception Data: 0000000000000008
OS Version: 10.0.18362.2.0.0.256.4
Locale ID: 1033
Additional Information 1: f5c3
Additional Information 2: f5c3901b05a3140a6dfabbc332a93f50
Additional Information 3: 9fd8
Additional Information 4: 9fd80debcb93fdb0aa26667b67200f58
Extra information about the problem
Bucket ID: edf7209e6fcd899069cfdb93400cd7c1 (1859946596608563137)
I can't use edge to submit the feedback because it doesn't work.
Beta works fine.
Jan 14 2020 07:03 AM
Jan 14 2020 07:07 AM - edited Jan 14 2020 07:10 AM
You can use this form to submit your feedbacks too:
https://microsoftedgesupport.microsoft.com/hc/en-us/requests/new
Sent from Android Mobile
Jan 14 2020 07:13 AM
Jan 14 2020 08:49 AM
Jan 14 2020 09:05 AM
@Rick Bertuzzi
Hi Rick,
I cannot repro the behavior you mention. Nothing I do causes crashes, not with this current Build nor past Builds. Try uninstalling & redoing it with a new download of Dev & see if it makes any difference. Are your other Channels ok?
Cheers,
Drew
Jan 14 2020 09:29 AM
Thanks for the reply Drew. I'll see if I can find a way to reproduce the issue consistently and post the steps. I saw this exact issue mentioned in a previous build release notes (Fixed an issue where closing a tab sometimes causes the browser to crash).
Regards,
Rick
Jan 14 2020 10:09 AM
@Rick Bertuzzi
No worries, Rick. See what Josh or Missy has to say about it, too, for what reply an, actual, MS / Edge person may offer. So often something arises that is not seen on all machines.
Cheers,
Drew
Jan 14 2020 10:12 AM
Jan 14 2020 12:43 PM
Jan 14 2020 01:25 PM
@javicuasih wrote:
Is it able in all countries?. Can not update in Spain
Cannot update to 81.0.381.0 ?
maybe try uninstall and then reinstall it from here