Edge problems
-
Platform info: Edge 40.15048.0.0. Latest "slow ring" Windows 10 insider release (but the bug has been there for a while). Tested on private mode (so no cookies), no browser extensions.
Clicking on a /post/[number] link, for example a notification or any of the permalinks inside a thread, shows an error page:
Internal Error.
Oops! Looks like something went wrong!Reloading the page takes you to the post. Entering the URL, or opening in a new tab also works fine. So it must be a javascript link handler thing. No error messages whatsoever in the debug console. Also the "/topic/[number]/[name]/[post]" links work fine.
So I went to community.nodebb.org to see if the problem happened there, and... well, this:
Page just reloads continuously ಠ_ಠ
-
-
@HardwareGeek But it's the fastest browser according to Microsoft. And Microsoft wouldn't lie to me.
-
-
@anonymous234
Hey, by the way, I have this amazing prime vacation land in Florida, it can be yours for a really cheap price!
-
@El_Heffe said in Edge problems:
@anonymous234 said in Edge problems:
Platform info: Edge 40.15048.0.0.
40?
I think that might be the global build number.
Since I believe the second number is the Windows release #, and the other two appear unused.
-
So, who do I have to yell at to finally get someone to look at this? Seriously.
-
Oh, I keep forgetting to mention, this happens on Mobile Edge too.
-
@Rhywden Well, at least community.nodebb.org no longer refreshes continuously, so that's an improvement.
Maybe we should mention @julianlam.
-
-
-
-
So, I use Edge at home and haven't seen that sort of craziness, but I'm not in any prerelease rings.
-
@Magus Started happening to me after the Creators Update
-
@Jaloopa I guess I'll also try reproducing it when I get home, though at most that'll just be, "Yeah, me too!" - no real hope anyone will fix it.
-
Just a heads up - I just updated to the latest Insider build and the bug seems to be fixed.
Since I didn't iterate through all the Insider builds I cannot tell you who fixed it (was it an actual Edge bug or some polyfill of NodeBB gone wrong?) or when it was fixed.
But fixed it is.
?
