Index Thing


Browser Compatibility

User Agent (browser) appears to be -

MOZILLA on Windows (Gecko based) SEA MONKEY on Windows (Gecko based) FIREFOX 2 on Windows (Gecko based) FIREFOX 2 on OSX/Mac (Gecko based) FIREFOX 3.0 on Windows (Gecko based) FIREFOX 3.5 on Windows (Gecko based) FIREFOX 3.6 on Windows (Gecko based) FIREFOX 3.7 on Windows (Gecko based) FIREFOX 4.0 on Windows (Gecko based) FIREFOX 5.0 on Windows (Gecko based) FIREFOX 6.0 on Windows (Gecko based) FIREFOX 7.0 on Windows (Gecko based) FIREFOX 8.0 on Windows (Gecko based) FIREFOX 9.0 on Windows (Gecko based) FIREFOX 10.0 on Windows (Gecko based) FIREFOX on Windows (Gecko based) FIREFOX 3.0 on OSX/Mac (Gecko based) FIREFOX 3.5 on OSX/Mac (Gecko based) FIREFOX 3.6 on OSX/Mac (Gecko based) FIREFOX 3.7 on OSX/Mac (Gecko based) FIREFOX 4.0 on OSX/Mac (Gecko based) FIREFOX 5.0 on OSX/Mac (Gecko based) FIREFOX 6.0 on OSX/Mac (Gecko based) FIREFOX 7.0 on OSX/Mac (Gecko based) FIREFOX 8.0 on OSX/Mac (Gecko based) FIREFOX 9.0 on OSX/Mac (Gecko based) FIREFOX 10.0 on OSX/Mac (Gecko based) FIREFOX on OSX/Mac (Gecko based) CAMINO on OSX/Mac (Gecko based) EPIC on Windows (Gecko/FF based) DOCZILLA on Windows (Gecko based) K-MELEON on Windows (Gecko based) NETSCAPE 8 on Windows (set as Mozilla) NETSCAPE 8 on Windows (set as IE) OPERA 9 on Windows OPERA 10 on Windows OPERA 11 on Windows OPERA 7 on Windows OPERA 8 on Windows OPERA 8 on Windows (set as IE) OPERA 8 on Windows (set as Mozilla) OPERA 9 on Windows (set as IE) OPERA 9 on Windows (set as Firefox) OPERA on Windows INTERNET EXPLORER 5 on Windows INTERNET EXPLORER 6 on Windows INTERNET EXPLORER 7 on Windows INTERNET EXPLORER 8 on Windows KONQUEROR 3 on Linux (WebKit/KHTML based) KONQUEROR 4 on Linux (WebKit/KHTML based) SAFARI on OSX/Mac (WebKit based) SAFARI on Windows (WebKit based) SAFARI 3 on OSX/Mac (WebKit based) SAFARI 4 on OSX/Mac (WebKit based) SAFARI on iPad/iOS (WebKit based) SAFARI on iTouch/iPhone/iOS (WebKit based) GOOGLE CHROME on Windows (WebKit based) GOOGLE CHROME 2 on Windows (WebKit based) GOOGLE CHROME 4 on Windows (WebKit based) GOOGLE CHROME 9 on Windows (WebKit based) GOOGLE CHROME 10 on Windows (WebKit based) IRON 4 on Windows (Chrome based) IRON 6 on Windows (Chrome based)

Cookies are used solely to hold the Display Width setting status - wide or normal.
All the pages should be XHTML 1.0 Strict and at the moment will be served as text/html - the next step would have been to serve the files as application/xhtml+xml with the .xhtml file type using content negotiation on the server however it is likely that the site will migrate to HTML 5 instead.
Not using HTML5 yet but XHTML 1.0 Strict pages work OK in browsers optimised for HTML5 and will be treated as similar to XHTML5.
Efforts are now focused on satisfactory working in mainline modern browsers that support HTML5 eg: Chrome, FF , Opera, (if Edge works fine but I'm not overly worried anymore).

All below is legacy .......

This web design uses XHTML and CSS (Cascading Style Sheets) extensively which provides a more structured layout however the layouts will not be supported in older browsers. Some of the newer browsers can also struggle to interpret the standards in a consistent manner so whilst effort is made to keep breakages to a minimum this is my best shot so far! 

Special note: IE7 has ClearType font rendition enabled by default. I find this awful on an LCD as the words are fuzzy and lack definition. The setting can be disabled in the Advanced options of IE7.

Design note: The main style sheet used is designed for and works with Mozilla based browsers. Chrome,Opera and IE7/8 largely conform to this style sheet also. However the CSS engines for IE6 and earlier versions of IE are not consistent and so require tweaking style sheets.

This site now uses a special javascript file that allows IE6 to interpret CSS similar to that of IE7/8/9. The IE6 pages will now render the mozilla-based stylesheet reasonably well with a few anomalies but unfortunately on page load there will be c. 7 seconds delay. The previous hack method for IE6 worked a lot better performance wise but required alternative stylesheets whereas the new method only requires the base stylesheet which does most browsers. The bottom line is that IE6 on this site (a few anomalies apart) will now render in a similar fashion to later/newer browsers but with a big (hippo-sized) performance penalty so therefore maybe it is time to try one of the later browsers!
Also see Special IE Note below.

Minor tweaks for various browsers are also handled in CSS via a browser detection javascript so some anomalies may occur when javascript is disabled.

Javascript is also used in the photo galleries (Thickbox)

I expect the site to work reasonably well with -

Firefox 3.6 (tested)
Firefox 4/5/6/7/8 ...... 16 (some tested but version changes too often!)
Firefox Nightly (as at ver 19 - tested on Snow Leopard 10.6)
SeaMonkey 1.0/2.0 (Mozilla based - tested)
Epic 1.2 (Mozilla based - tested)
IE 8 (tested - very slow javascript rendition on some pages)
IE 7 (tested - very slow javascript rendition on some pages)
Google Chrome 15 (tested)
SRWare Iron 13 (Chrome based - tested)
Opera 10.0/10.5 (tested)
Opera 11.0 (tested)
K-Meleon 1.0/1.5 (tested - based on Gecko/Mozilla - Faaasst!, hot stuff)
Camino 2.0 on MacOS X (tested on Snow Leopard 10.6 - uses FF 3 rendering engine)
Safari 5.1 on Windows (tested)
Safari 5.1 on MacOS X (tested on Snow Leopard 10.6)
Safari 4.0 on MacOS X (tested on Tiger 10.4)
reKonq 0.7.0 (Kubuntu 11.04) (tested - linux fonts rough - webkit based)

Lynx 2.8.3 (tested - not too bad for a text based browser)

Opera 12 is buggy on the scroll and some small layout issues - this isn't unusual for Opera - Moz and Chrome always pretty good but Opera always manages to break something!

 Not Hippo friendly or recently checked - Take your chances!

Not tested recently indicates that no problems were apparent when they were last tested so maybe they still work?

IE9 ( I don't have Win 7 since XP and OSX are more than sufficient however I will try to get round to it maybe one day although it should be fine ) IE 6 (tested using emulator - slow performance)
IE 5.5 SP2 ( not tested recently )
IE 5.01 SP2 ( not tested recently )
Mozilla 1.0 - 1.8 ( not tested recently )
Firefox 1.0/1.5 ( not tested recently )
Firefox 2.0/3.0/3.5 ( not tested recently )
Netscape 7.0/7.1/7.2 (not tested but they use Mozilla codebase)
Netscape 8.0 ( not tested recently )
Deepnet Explorer ( not tested recently - based on IE)
Safari 3.2.1 on MacOS X ( not tested recently )
Safari 2.0.2 on MacOS X ( not tested recently )
Firefox 3.X on MacOS X ( not tested recently )
Camino 1.8 on MacOS X ( not tested recently )
Konqueror 3.2(Mandrake Move) ( not tested recently )

Opera 9.1/9.2/9.5/9.6 (DW breaks layout )
IE5 on Mac (not good, CSS links and NAV busted - use FF or Safari)
IE 4.01  (layout busted - can navigate )
NS 4.XX (degraded but useable content available, text nav possible)
IE 3
Netscape 3.0
Netscape 6.0 (not tested - possibly OK with some bugs maybe)
Opera 3.11/5.0/6.0 ( not tested recently )
Opera 7.21 ( not tested recently )
Opera 7.54 ( not tested recently )
Opera 8.0 ( not tested recently )
Opera 8.5 ( not tested recently )(agent id should be set for Opera)

Amaya 11.3 - (Average - more an editor though)

Designed for 800 x 600 at least and a DW option (Display Width) to cater for 1024 x 768 and larger.

Special IE note

This site uses curvy corners which are supported by most modern browsers (CSS3 feature - border radius) however IE7 and IE8 don't support this feature and whilst they can be made to render the pages correctly by using javascript code unfortunately the performance is poor due to the slow javascript speeds within IE.

This is a shame since the rendering is usually good however I've found that a really good way of improving the javascript performance of the IE browsers is to install the Google Chrome Frame plugin which allows IE to be used as normal but the page rendition will be done by the Chrome Frame engine.

The Hippo will allow use of the Google Chrome Frame for IE8 and below only - other browsers should be just fine

Should you wish to use the Google Chrome Frame it can be installed from HERE

To disable Google Chrome Frame, follow these steps:

  1. In Internet Explorer, go to Tools > Manage Add-ons in the menu bar.
  2. In the "Toolbars and Extensions" section, select ChromeFrame BHO.
  3. Click Disable.
  4. Restart browser.