reporting Edge bugs at http://developer.microsoft.com for a day now and found a gazillion usability problems with the site. Why am I not surprised?
Now @MSEdgeDev will look at your bug and edit it. you'll get 0, 1, 2 or 3 emails every time they do. (I wonder if I can use that as a PRNG?)
-
-
Note that each email may or may not contain the comments the dev added, so click on the link to make sure. Maybe you want to reply?
-
Sign in then... it'll take you to https://login.microsoftonline.com/ (?) type your email, type your pa... huh? it's redirecting you to another page!?
-
Yes, to https://login.live.com/ . So you'll have to manually enter an email (any email) to get to the real login page... facepalm.
-
...so I enter my login credentials and it redirects me to https://login.microsoftonline.com/ !? Here I am apparently supposed to click on my account...
-
or click "use another account". Let's do the former... I get redireted to https://developer.microsoft.com/en-us/ !? So I open the link to the bug again...
-
...and it turns out I am not logged in. WTF!?!?
-
...and attaching a file when a file with the same name already exists silently fails, discarding the new file (https://developer.microsoft.com/en-us/microsoft-edge/platform/issues/7234780/ …)
-
...and if you forget to tell it what browser and version you found it in immediately after opening the bug, you cannot do so later.
-
@berendjanwever ...and there is no way to bookmark the issues your reported. You have to go to https://developer.microsoft.com/en-us/microsoft-edge/platform/issues/ … and click "my issues" -
@berendjanwever ...which shows only 8 issues, not all issues. AFAIK there is no way to do that. This is getting ridiculous. -
...and when you want to comment but need to log in first, you do not get redirected to the original issue page.
-
...and when MS devs say they will look at these issues, nothing happens for at least a week.
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.