Forum Discussion
Dev channel update to 80.0.355.1 is live
- Sync issues are the main reasons why I'm not using Edge as my default browsers. I've lost some of my favorites before due to sync issues and it wasn't an acknowledged issue.
RicoViking9000 there are two issues that we know about with the new tab page right now. One of them was due to a feature rollout that we stopped and pulled back. If you were seeing layout that looked weird or things that didn't load, it was probably that issue. Anybody who saw this should be back to normal by now. The other is an issue where the new tabs completely crash when they try to load. For some users, hitting enter in the address bar to try to navigate again succeeds; it's just the first navigation that won't work. We're still investigating that issue.
- For the first time ever in this 80.0.355.1 build, my New Tab Page is broken. I turned off the background image and ever since, the page just loads a blank gray page.
If I refresh, it'll show my Quick Links for a split second and then those disappear, leaving the initial blank gray page.
Absolutely unreproducible on my other two systems. Sigh, most Chromium Edge bugs are turning out like this: appear completely out-of-the-blue, have been repeatedly previously reported, and nobody's really got a clue how they come or how they go.
ikjadoon , @Drew1903 , @RicoViking9000
Thanks everyone for letting us know about the issues with NTP. Are you still experiencing these with the most recent Canary updates? If so, I will chat with our engineers about next steps.
Fawkes (they/them)
Project & Community Manager - Microsoft EdgeDeleted Thank you for listening.
I think after the feature rollout was halted, I've not experienced any similar or any issues otherwise with the NTP.
ikjadoon Get the same issue. Just reported with feedback. I noticed that NTP show some error in developer tools. Problem with cookies, tracking prevention which not load some resources and an error with javascript.
Edit: Suddenly NTP now works just fine
I'm seeing that too, tracking prevention set to balanced
ikjadoon
You raise a good point here. The fact that I do not have said issue nor can I repro it (and, believe me, I tried!) is an(other) example of the randomness of bugs. Oft the explanation given is "Controlled Roll-out Feature". But, that is not one machine or User affected and not another, by what is an overt bug; that's merely a delay or lag in receiving a new item.. Myself, as an example, there are, have been countless items mentioned in the Forum of problems, breakages, things amiss in one way or another, issues of some sort whilst, my 2 machines see none of the same... not withstanding "Known issues", of course.
Reading stuff one is not experiencing is perplexing OR the fact that something is not universally felt or seen is, if nothing else, interesting, maybe, intriguing. (even, unexpected). But, it does make one wonder at why. (Well, makes me curious, anyway)
The variables that can factor into causing this phenomenon are many, it's said. But, it is, certainly, noticeable that some are impacted & not others. Frequently, the 'bugs' are not hitting everyone. And, I will vouch for that 1st hand, to support the occurrence.Drew1903 Thank you kindly for trying to reproduce it; my apologies in the delay replying to your sincere testing. I was out of a working system for this week (not related to Chromium Edge, heh).
But, you're exactly right. Controlled "feature rollouts" in testing environments, especially buggy ones that have no discussion or introduction, have always been problematic for testers. It's a win-lose situation where the loss of autonomy by testers is the gain of autonomy by developers. Testers can't begin to write meaningful bug reports because "not reproducible" is a feature of these rollouts--our task as testers, on the other hand, should be engaging the product faithfully & describing its behavior via our access to "live, user" machines with myriads of physical hardware configurations, browser profile settings, and browsing patterns.
When you instead use "feature rollouts", testers are left in the dark. Does "not reproducible" mean it's a third-party issue unique to this system? Does "not reproducible" mean the trigger condition is too rare to produce spontaneously? Or, here, is this just another "feature rollout" that was enabled for just this machine?
Thanks for confirming, little_terry and HotCakeX . The same happened on my machine: once they reversed the rollout from this machine, the bug disappeared.
Cheers, josh_bodner , for the update on what exactly was going on. Definitely the former.
RicoViking9000
It's not 'broken' for me, in any way. In what way or ways do you find it to be 'broken'? Please, define or explain "broken", in this context. Thanks. Please, specify or detail the NTP behavior you have.
Cheers,
Drew
