« [Security] BBCode in SQL Database
Looks in IE and Edge.
Looks in IE and Edge.
« on March 6th, 2017, 03:39 PM »
Wedge is unusable in Windows 10 v11.576.14393.0
In Windows 10 Edge 38.14393.0.0 Wedge looks ok but I think it's not looking as it should.

Thought I let you know just in case you havend't noticed yourself.

📎 IE11.PNG - 9.17 kB, 457x297, viewed 180 times.

📎 Wedge.PNG - 8.54 kB, 331x205, viewed 192 times.


  • Dadman with a boy
  • Posts: 16,079
Re: Looks in IE and Edge.
« Reply #1, on March 6th, 2017, 06:03 PM »
Weird. Looks like a problem with the user agent string. I'll look into it.
Re: Looks in IE and Edge.
« Reply #2, on March 6th, 2017, 06:48 PM »
Fixed. Wasn't a problem with Wedge, but with a quick hack I wrote for Lestrade's and backported to Wedge.org (the website) by mistake.
The original problem was IE11 was unable to load compressed CSS/JS files on the new server I had. I managed to make it work in Lestrade's, but the actual solution was to remove gz extensions from the 'static' file list in the nginx configuration (it's a reverse-proxy server). Nginx used to catch gz files and directly serve them with their original MIME type, when it was supposed to pass them to Apache, which through the htaccess file was setting the MIME type to the correct one (i.e. text files).
I had the nginx config file fixed, so the fix was no longer needed. But I forgot to remove it, so IE11 kept serving these files uncompressed. And because of a final mixup between two fixes, I ended up serving uncompressed extensions with compressed content, so it broke the site when I updated it last night.


BTW, IE still sucks hard. :P
I'm not even adding support for Edge... After all Microsoft themselves are marking it as Chrome-compatible. So, I'll just let them fix everything by themselves, to me, Edge is an older Chrome build and that's how I'm treating it. (And probably how they want others to treat it, because let's face it, anything is better than being treated as a "newer IE".)

PS: I just found out that my first IE11 fix for this was from late 2014, so it couldn't be linked to the new server. Uh. I'm at a loss here. I'll just revert that revision (c3c77a3b22223eedce97f18b7ad719437b3dc154), and hopefully it works everywhere.

Re: Looks in IE and Edge.
« Reply #3, on March 6th, 2017, 09:12 PM »
Wedge in IE11 is looking great again.
Thanks Nao.

I agree IE11 sucks, but a few sites/things work better in IE11 then Edge. 
Edge is far from being complete. For instance you can't install certificates. You have to return to IE, or Chrome. Microsoft still has a long way to go before it will be the browser they promised it would be.
Although they work fine I am still no friend of Chrome, or Firefox.
Some days you have to use IE, Edge and Chrome to open all sites you need for your work.
I now it was a nightmare for developers, but as a user you sometimes wish back the IE only time.


  • Dadman with a boy
  • Posts: 16,079
Re: Looks in IE and Edge.
« Reply #4, on March 7th, 2017, 12:41 AM »
Edge has so many features that aren't implemented yet (https://developer.microsoft.com/en-us/microsoft-edge/platform/status/) that I don't consider them on the same level as Chrome or Firefox. In fact I'm pretty sure many people at Microsoft were considering switching IE to Webkit/Blink, but the W3C would really rather have as many different HTML rendering engines as possible (they were already quite pissed off that Opera gave up on Presto...)

Plus Edge doesn't really have the usage stats it's purported to have.

Opera Chromium + Sidewise extension are really the best for a power user.

PS: I don't remember having to use something else than Chromium to open a site in the last 3-4 years.