Friday, 05 April 2013
Now for anyone who has read the Code Guru's latest blog post you will know we are not a fan of non standard compliant web browsers here at Symphony Towers. Cross browser testing for defunct browsers can be very time consuming, restrictive and extremely difficult to do.
So while we certainly can not guarantee that the websites we build will function and look the same for every user (the variables of device, browser, configuration etc make this extremely difficult) we believe our testing process is pretty darn good.
So what do we do? I hear you ask
Well we test all our website builds with the following devices and browsers:
Apple Imac 27" (Snow Leopard 10.6.8) - Running Firefox, Chrome and Safari (latest versions)
Apple Mac book Pro 13" (Lion 10.7.5) - Running Firefox, Chrome and Safari (latest versions)
Apple Ipad 3 (IO S 6) - Running Safari and Chrome
Apple Ipod Touch (IO S 6) - Running native Browser
Google Nexus 7 (Jelly Bean) - Running Native Browser
Samsung Galaxy S2 (Jelly Bean) - Native Browser, Firefox (Android), Chrome (Android)
Samsung Galaxy S2 (Ice Cream Sandwich) - Native Browser, Firefox (Android), Chrome (Android)
HTC Desire Z (Gingerbread) - Native Browser
And finally this is the big one
PC (Windows 7) - Running Firefox, Chrome, Safari and IE9 plus a virtual machine set-up with windows XP running IE6, IE7 and IE8 (Below I will go through how we set this up)
Now this is 'our' solution not 'the' solution and as I mentioned before there are so many varying factors that you can never know exactly how a website will manifest itself to the end user but we hope this gives us half a fighting chance.
The most complicated part of this was setting up a Windows based machine to run the older versions of IE, below are some instructions on how we achieved this:
1. We started off with a fresh install of Windows 7 on some crusty old PC that previously had the dual functionality of doorstop and foot rest. We updated the IE version on this to 9 and downloaded Firefox, Chrome and Safari (just to make ourselves feel better).
2. Now because our choice of software for running IE7 and IE8 requires XP so next we installed windows XP mode onto our Windows 7 PC and then set up a virtual machine. The link to this is here http://www.microsoft.com/uk/windows/virtual-pc/download.aspx and you basically need to download and install Windows XP Mode, Windows Virtual PC and Windows XP Mode Update then follow the instructions at the bottom to set-up the Virtual Machine (this process was time consuming but fairly straight forward).
3. So we now have a Windows XP virtual machine living within our Windows 7 OS (sounds like a train wreck doesn't it). Next we needed to get the older versions of IE running on this virtual machine (6, 7 and 8). IE6 comes bundled with XP Mode as its default browser so big tick there, now IE7 and IE8. To do this we used Utilu's IE collection (http://utilu.com/IECollection/) once you can navigate through Softpedias complex download process (normally the download link most hidden and inconspicuous is the one to click) installing this is pretty easy. We unticked all options other than IE7 and IE8 (I mean IE1 to IE5.5 really? we are not that hard on ourselves) and then dragged a couple of shortcuts to the desktop.
So now we have a stand alone PC machine (you really wouldn't want to be using this for much else) with Windows 7 and XP running Firefox, Chrome, Safari, IE9, 8, 7 and 6 (Ever so slightly more useful now than as a foot rest or doorstop).
If you have any good advice or set-up's for cross browser testing please drop us a comment as I believe that this is always going to be a moving target.
Did someone mention IE10 Ahhhhhhhhhhhhhhh!
Have you ever wanted to force a HTTPS connection for your ExpressionEngine website? If so, you may have also wanted to 'unforce' that connection for other areas of your website, either for performance issues or because maintaining both HTTP and HTTPS for the same section can be tricky. Avoid those pesky browser warnings about unsafe (non HTTPS) assets with this htaccess rewrite.
Everything looks better with an oilslick filter #Fireworks-- Delivered by Feed43 service11 Feb 2014 | 9:04 pm View full tweet
@meloncreative cool just be warned that the documentation for Form Integ. is incorrect, so if you are relying on it there are some gotchas-- Delivered by Feed43 service9 Jan 2014 | 5:39 pm View full tweet
@meloncreative do you need any sample code for the Form Integration?-- Delivered by Feed43 service8 Jan 2014 | 9:35 pm View full tweet
Thanks for your message! We will get back to you ASAP!