Awasu » Fixing Awasu’s embedded browser
Thursday 8th October 2015 1:56 AM [Awasu News]

Awasu, of course, uses an embedded Internet Explorer browser to show web content, but it's always bugged me that rendering never seemed to be quite the same as a standalone browser.

I've finally figured out what was going on :jig: [1]Although to be honest, it should've twigged a long time ago. I guess sometimes I'm just a bit slow... 🙄 - while all the documentation says that the installed version of IE will be used, what they invariably forget to tell you is that it's in IE7 compatibility mode :bigshock:

My usual :wall: emoticon is clearly totally inadequate at this point, I need a little yellow man blowing his brains out with a shotgun, or something like that 👿

I'll include a fix for this in the next release, but fortunately, the temporary fix for this is straight-forward: just download and run this file[2]It adds an entry to the Registry saying that awasu.exe should run IE11 for embedded browsers.. If you want test it, open the forums (from within Awasu) and check that the navbar across the top is displayed correctly. Sites using HTML5 and all that other new-fangled frippery should also work a bit better now. Sigh...

/taka toddles off to find a new smilies pack to install... :bah:

   [ + ]

1. Although to be honest, it should've twigged a long time ago. I guess sometimes I'm just a bit slow... 🙄
2. It adds an entry to the Registry saying that awasu.exe should run IE11 for embedded browsers.

2 Responses to this post

From the web developer view those "compatibility modes" have given me hours of headaches with CSS formatting over the years. Forgetting a certain HTML or CSS setting will trigger "compatibility modes"; once you remember to explicit set a
"X-UA-Compatible" value life gets a little better.

The problem I have is that I can't rely on any of those settings - if someone clicks through a link, then they get whatever page they requested, which is out of Awasu's control. This is probably why it took me so long to fix this 😐 since I generally open links in a browser outside of Awasu 🙄 But every time I looked at it, I was barking up the wrong tree - because it wasn't rendering correctly, I assumed the wrong version of IE was being loaded, but the browser was reporting the correct version (which indeed it was), so I was getting very confuzzled. This is what happens when you let backend developers loose in a browser... :wall:

Have your say