Posted by david
on 18 May 2010 at 20:30
I’ve been working on an HTML5-based offline web application but ran into trouble when updating files listed in the cache manifest.
Even though the files were downloaded and cached when the page was initially loaded, if a change was made to one (or more) of the files listed on the server, the browser detected the updated manifest file and began pulling down the updated file(s). However, the update would halt with an error part way through the process, but only in Firefox; the update process worked fine in Safari and Chrome.
Posted by david
on 30 Mar 2009 at 15:54
A week or so after upgrading Firefox to 3.0.7 on my Linux system, I began running across an occasional web page that wouldn’t render correctly. At first I attributed it to poor page coding — perhaps one of those old-timers that still hasn’t learned that there’s more to web browsers than IE, or someone who mucked up their CSS and wound up with white text on a white background — but since I wasn’t necessarily in need of the information at the site, considering the Google search that took me to the site provided many more possible links, I just moved on to the next site without bothering to figure out why the page didn’t render.
Unfortunately, the frequency of pages not rendering properly began to increase to the point that I began experiencing the problem with web sites that I did need to access. Opera could render them fine, and Firefox on my Mac OS X system had no problem, but Firefox on Linux was a basket case. Even worse, Galeon and Seamonkey crashed when I tried to visit those same sites.
