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.
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.
Deleted
Myself, I only ran into just one very specific scenario. It, still, exists. Web pages are Dark without a flag enabled for both Dev & Canary on 2004, exclusively. This is not the case on 1909. Other than that no issues, at all. And, should be noted, tested same on someone's 2004 in Florida and their's did not stay Dark with the flag set to Default. Certainly, inconsistency is nothing new or strange to us.
And, now, on my own 2004, as well, both Dev & Canary are only Dark with the flag Enabled. That part is behaving properly (mystically & suddenly). However, both are, still, requiring the Collections flag.
But, no issues with NTP not, now or previously. If we have to have a NTP, wish is was actually, Bing.com. By the same token, being a Bing Insider, I have recommended the same Custom choices for Bing.com as there are for the NTP.
Cheers,
Drew- If the NTP is going to get the theme of the default search engine then we should be able to change that to any search engine we want. such as DuckDuckgo.
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.
- Nice in-depth explanation. I hope after Edge stable is released and the rate the new features are introduced in Edge insider is decreased, the controlled feature roll out go away and everyone in the same channel (Canary/Dev/Beta) have access to the same set of features.
just like in google chrome.
- It's okay, due to controlled feature rollout, not everyone's browser and experience is the same, so it's normal if only a specific group is experiencing a problem.
