The latest version of Mozilla Firefox 220.127.116.11, I’m sorry to report, broke a couple of our web pages yesterday.
UPDATE: This problem has now been fixed in Firefox 18.104.22.168: see Firefox 22.214.171.124 update to be updated
I noticed it just as I was about to go out for lunch. I was checking out a page on the University website and followed a broken link … to a broken 404 page.
At first I simply suspected that it was due to some CSS tinkering that either my colleague or I had done. But neither of us had done any.
And then I discovered that it was working fine in Firefox 1.5, IE6, IE7, Opera 9 and Safari 3. It was working fine in my colleague’s installation of Firefox 126.96.36.199 … and then when he restarted the browser to allow its automatic update to version 188.8.131.52 it promptly broke.
So the culprit was indeed the latest incarnation of my favourite browser. How disappointing.
The way that the page is constructed is that there is a
div that wraps the page’s main content. If I was recoding it today, I’d call it
#contentWrapper; when I coded it 10 months ago, I called it
#main there are three other divs, in order:
#main then has a background image of part of the University crest. How much of the crest is displayed depends entirely on the height of its three internal divs.
Only, this appears to be the problem that Firefox 184.108.40.206 has highlighted/discovered/introduced* (*delete as applicable): it now does not recognize the height of the internal divs:
#related_content and so collapses, as you can see from the screenshot above.
The (temporary) fix
min-height CSS attribute to the code has temporarily fixed the problem, but fixed the height of
#main at 550px — enough for the 404, 401 and the front page, which all use that code.
I’m now working on a more robust fix … in fact, I’m now working on recoding the entire site to make it more usable by the few ancient browsers that Google Analytics informs us are still being used to visit the site, such as Firefox 1.0, Firefox 1.5, and various older versions of Netscape and IE.
- I wanted the site to be as accessible as possible, and decided that placing the main page content as high in the source code as possible would be helpful.
- Do you know how difficult it is to achieve something as seemingly simple as creating a page layout with three equal-height columns?
- The ‘holy grail’ approach worked for almost everything we needed until it came to wanting to jump down to page anchors. We had a couple of A-Z lists and wanted to be able to click on ‘D’ to take us down to the ‘D’ entries. Instead, it pulled ‘D’ up to the top of the page and made A-C disappear completely!!
- We decided to fully support only modern browsers: IE6 and IE7, Firefox, Safari/Konqueror and Opera 8 and above. (While I don’t class IE6 as a modern browser it’s the one used on about 75% of all the university PCs so we had no choice but to support it.)
I guess I now need to be finishing writing these fixes sooner rather than later. I’m just a little disappointed that the latest version of my favourite browser has broken the code, while Safari, Opera 9 and even IE7 saw fit to render it as expected.
However, what I’m not entirely certain about is whether Firefox is now simply rendering the code as it should be (in other words, I’d missed a trick with my code) or whether this genuinely is a fault with Firefox’s rendering. Time will tell.