Forum Discussion
Edge Dev Branch update?
lwetzel "Is there a way to find out what changes have been made in the updates?" Not yet, to my knowledge. Quite a number of us have requested that changelogs and other normal test-team information be distributed with each updated version, and the MS reps on the board have acknowledged that MS knows that there is a need for this information to facilitate testing.
tomscharbach -- Yeah, I am one of those who asked for changelogs. I find the system frustrating as it stands. For example, last week I complained about Edge's behaviour when handling Facebook pages. It only loads a few posts at a time and I constantly have to click on More Posts. That behaviour is absent from Brave, Chrome and Vivaldi... and the soon to be deceased Edge. There have been at least four Canary updates since I reported the problem and it's still not working properly.
I am not complaining that it has not been fixed. yet I am frustrated because MS leaves us in the dark. What am I supposed to do? Check if the bug is still present day after day, and report it day after day? Or do I trust that MS will eventually fix it? What if MS programmers believe they have solved things but it's still not working for me. How am I supposed to know if they are finished working on displaying Facebook pages, meanwhile they wouldn't know that it's still broken at my end.
I am using this example because earlier this evening, it looked like the pages were loading properly and I didn't have to click on More Posts every 5 seconds. But that lasted for only 2 or 3 minutes. Now it's still showing the same bad behaviour.
What am I supposed to do? It's certainly not among the pinned posts and we have no changelogs. I am glad to be able to test Edge and help the development team. I just wish there'd be a better system of reporting and checking whether things have been fixed or not.
NicolSD "I am frustrated because MS leaves us in the dark." I am too, along with lots of others. I'm used to testing in an open source environment where the test group has access to a development list, a known issues list, changelogs, and "test this, test that" direction as features/functions are added. MS is much more closed down in W10 Insider testing, and probably across the board. All I can say is that Elliot Kirk, who is a software engineer on the Edge team and who monitors this forum, has acknowledged the problem and told us that it will change. If we keep the Edge team's feet to the fire on this, it will probably happen.
- tomscharbach -- I hope I did my bit to help keep the Edge team's feet to the fire with my comment. So far, I have received two replies to my frustration comment but no answer as to what I am supposed to do, ie. what am I do regarding bugs that may or may not have been fixed. I take it that my frustration about that is shared.
NicolSD Your frustration is shared by a lot of folks, based on the number of comments about the issue.
As to what to do about a reported bug/issue, I don't know. I read your question as being addressed to the Edge team, and obviously I can't answer for them.
I plan to log the bugs/issues I report through the Feedback node and check on progress as I get updated Dev builds each week, taking reported bugs/issues off the list as they are fixed. The development process is going to take months, and I'm most concerned about getting accurate information about reported bugs/issues so that I know something I've reported is on the list. If and when we get a "known issues" list, then I won't have to do my own logging, and I'd like that ...
Same here I also asked for changelog....Its too frustating.