On 19 June 2013 21:56, Justin Ross <[email protected]> wrote:
> On Wed, Jun 19, 2013 at 11:01 AM, Rob Godfrey <[email protected]>
> wrote:
> > On 19 June 2013 16:58, Justin Ross <[email protected]> wrote:
> >
> >> On Wed, Jun 19, 2013 at 7:17 AM, Robbie Gemmell
> >> <[email protected]> wrote:
> >> > Hi Justin,
> >> >
> >> > I had a quick lookand noticed a few issues:
> >> >
> >> > The site can't be used at all in IE8 as it loads up in XML view. This
> >> seems
> >> > like a blocker to me, as IE8 is apparently still one of the most used
> >> > browsers.
> >>
> >> I've added an attempted fix, a meta header that the internet says may
> >> have a positive effect. Unfortunately, right now I don't have access
> >> to IE8; I can try to install it tomorrow. Could you give the head
> >> site another try and let me know if there's any change?
> >
> > Nope - still seems to be broken :-(
>
> I believe I've got this fixed now. I removed the standard template's
> xml declaration. (It's still all xhtml). I used browsershots.org to
> render the page on many browser versions, since I don't have access to
> a windows machine today. With the latest change, it seems to render
> well enough all the way back to IE6.
>
> Justin
>
>
I gave it another look in IE8 and the site now renders, though it does so
with an error indicated and much of the styling for headings, navigation
highlighting, column layouts, fonts etc doesn't seem to be as intended.
In particular it is complaining about an object not having a method at Line
188 char 1 of site.js, which seems to be: window.addEventListener("load",
registerEventListeners, false);
It's usable in a pinch but can be quite hard to follow, particularly for
the documentation etc.
I also just noticed that the search image in the top right and the Apache
feather image in the footer navigation gets a blue border in IE (8 and 10,
which seems to otherwise match Firefox 21).
Robbie
