Discourse dislikes Edge?

I keep running into issues using Discourse with Edge…

Drafts magically being edited in “another tab” (no other tabs open).
Links not being clickable, including the topic names in the main view…

Have you run Edge on the site while leaving the dev tools console window open? Do you happen to see any errors pop up when you see the links are unclickable and such? Perhaps there is some kind of Edge specific JS error that is causing the page to not render things properly.

I am not seeing these issues through Edge in testing but it is weird that it wouldn’t work and something like Chrome would since they are pretty much the same engine behind the scenes.

If you are able to catch the issues pop up in dev tools, then perhaps you can isolate the issue in Edge.

I mean, take your pick…

Ooof… That is bad. Do all those show up in your Chrome too?

I use Edge and, unusually, don’t have any trouble on here. I’m not as prolific a poster, though.

I do have problems with Facebook, clicking on things doesn’t do what it should. That might not be Edge, though it seems to have taken over from IE at being blamed for stuff.

Looks like you’re having issues with the discourse CDN. Do you have an aggressive ad blocker running that you don’t have in Chrome or anywhere…maybe? Possibly?

I’m grasping at straws because I can’t duplicate it in Edge at all after about ten minutes of trying, and like Martyr2 says, Chrome and Edge are pretty much the same in the rendering engine so it wouldn’t make much sense to have issues with one and not the other…

Chrome doesnt… dislike it as much as Edge, but it still dont like the inline scripting :stuck_out_tongue:

EDIT: And then after a while it throws these…

I should respond to the other point… “Do you have an aggressive ad blocker running”… possibly, but at the same time, not one that i’ve installed recently. So something’s changed; either the browser, the ad-blocker’s own inbuilt stuff, discourse, or something in sitepoint’s specific implementation.

That should be easy to test. Do you see the same kind or number of errors when visiting other Discourse-based sites? There are lots of them listed here: https://www.discourse.org/customers

You could also try on another computer. That would at least remove the idea that it is sitepoint based because if it is not showing up on other computers and is only on your one computer, then it might be something you have installed or configured locally.

Well its not Sitepoint specific, at least… the SmartThings one is doing the same thing while looking at the Latest… It… looks like this line is the one responsible there:
Refused to execute inline script because it violates the following Content Security Policy directive: "script-src https://community.smartthings.com/logs/ https://community.smartthings.com/sidekiq/ https://community.smartthings.com/mini-profiler-resources/ https://global.discourse-cdn.com/smartthings/assets/ https://global.discourse-cdn.com/smartthings/brotli_asset/ https://community.smartthings.com/extra-locales/ https://sea1.discourse-cdn.com/smartthings/highlight-js/ https://sea1.discourse-cdn.com/smartthings/javascripts/ https://sea1.discourse-cdn.com/smartthings/plugins/ https://sea1.discourse-cdn.com/smartthings/theme-javascripts/ https://sea1.discourse-cdn.com/smartthings/svg-sprite/ https://www.google-analytics.com/analytics.js 'sha256-rwfdvotzygqmkowfnaex564b66behoel4+grlgqughg=' https://www.googleadservices.com/ https://*.google-analytics.com https://smartthings.us5.list-manage.com/subscribe/post-json https://www.googletagmanager.com/gtm.js". Either the 'unsafe-inline' keyword, a hash ('sha256-rwfDVOTzygQmkOwFNAeX564B66beHoel4+gRLgQUgHg='), or a nonce ('nonce-...') is required to enable inline execution.

It… reads like something has changed in Edge’s security as regards inline scripts, and is causing… I’m not sure what. There’s definitely still an anchor tag in the source code, that appears to be rendered on the screen, but from my poking around with the Inspect tool, there’s a “splash” overlay on top of the forum that’s obstructing the mouse from reaching the content… when i do the same test on the sitepoint page, my Inspect tool lands here: