02-05-2020 10:36 AM
02-05-2020 10:36 AM
Hello Insiders, today we’re releasing build 81.0.410.1 to the Dev Channel. We’ve also got our quarterly survey available to take here: https://techcommunity.microsoft.com/t5/surveys/quarterly-survey-january-2020/m-p/1138394. Please let us know how we could better interact with you on the Tech Community forums!
Next, we’ve got a new how-to over on the Enterprise section: how to disable the First Run Experience: https://techcommunity.microsoft.com/t5/enterprise/how-to-hide-the-first-run-experience-in-the-new-mi.... There’s also a new blog post explaining our work to localize the F12 Dev Tools: https://blogs.windows.com/msedgedev/2020/02/04/localizing-edge-devtools/. Finally, all of the most noteworthy features and fixes for this week:
We expect next week to be the final Dev release for version 81. In the meantime though, thanks for all your suggestions and all the bugs you’ve found!
02-05-2020 11:41 AM
Issue, when after installing this update my Favorites bar had many duplicates.. see photo below.... Also, links that I had set to "show icon only" were changed to show both, icon and text/label.... Sending an "x-Mr. Smiley" on the issue as well...
02-05-2020 12:26 PM
You asked: "Please let us know how we could better interact with you on the Tech Community forums!"
It would be very nice if when someone asks for a feature and states that for them it is a NECESSARY feature, i.e. without that feature they will NEVER use Edge, someone from the dev team would engage and say whether it will be considered, is being considered, is in development or simply will never happen. I'd be much happier with Microsoft if you'd just tell me the feature I have said I require many, many times over many, many months can't and won't happen than I am being left dangling, reading these threads after every release, trying Edge to see if that feature has appeared after every release, and ending up frustrated and feeling I am wasting my time.
It would also be helpful to you, I would have thought, if you invited users when they request things to distinguish between things they would LIKE and things that to them are NECESSARY (i.e. without which they absolutely will not use the software).
02-05-2020 01:32 PM
02-05-2020 01:37 PM
@DavidGB I understand your frustration, I'm a user of my own product, and there are still features that I'm waiting for that make it very difficult to use in the meantime (in my case, I use lots of tabs, so having them squish down to an itty bitty size makes it almost impossible for me to figure out which one I need at any given time).
The problem is that nobody can give you a definitive answer because there are no definitive answers. I'm never going to say something will never happen, because never is a long time, and we don't plan on stopping or slowing down development any time soon. Everything is just a question of priority: how many users are asking for something, how bad the problem is that needs to be solved, what workarounds there are, how hard is it to deliver, what do our competitors offer, etc. And in my years on the browser team, I've learned that everybody has that one "killer" feature that they absolutely need, and rarely is it the same as anybody else's killer feature.
So, as we continue to finish up the features we're working on, we constantly re-evaluate our priorities and decide what to work on next. And if that comes off as being non-committal, I apologize, that's not the way we want it to seem. It's just hard for us to say "well, we think we'll be able to get to it in 6 months" when we don't know what other priorities are going to come up in 6 months once our current set has been delivered. Maybe Google is working on this in Chromium and we'll just get it for free. Maybe it's actually really hard to implement in Chromium's codebase and we won't know that until we start working on it. In the meantime, yes, helping us understand why it's important to you does help us, especially when you tell us why it's so necessary, not just that it is.
02-05-2020 05:17 PM
@sialivi the visual glitch is completely random and not caused by any user actions, although highlighting the text should fix it (at least until it happens again). It's caused by an upstream Chromium bug, and we received the fix for it from them earlier this week, so it should make it into the next Dev release.
02-05-2020 11:49 PM
02-06-2020 12:23 AM - edited 02-06-2020 12:24 AM
I understand that it isn't something that was caused by this software specifically, as you said it was chromium. But thought I'd make it known (in case it wasn't) that more recently for myself, highlighting the text does not always fix the visual glitch.