In article <[EMAIL PROTECTED]>, JTK wrote: > Bradley Baetz wrote: > >> >> So, noone else is seeing this. > > > Nobody else is admitting that they see this.
If you really think that there's a conspiracy by Mozilla/AOL-TW/the Trilateral Commission to suppress all the failed smoketests that this bug would cause, and all the reports from the community of relatively disinterested bug reporters (e.g., those not involved in the Mozilla community and presumably not blindly pro-Mozilla or however you care to designate us), I would respectfully suggest lithium. That a smoketest blocker on one of the more popular and frequently accessed websites on the WWW would go completely unnoticed by anyone is, quite frankly, an extraordinary claim, and requires commensurate proof. > >If you go to advanced->cache in your prefs, > >> what are the cache settings? It should be set to automatically. >> > > > As I replied to Pratik below, it's set to "when out of date". > Four-day-old CNN should qualify I'd think. The closest I could find was bug 78551, but I don't think that would apply, unless you've had your browser instance open for four days. Does this occur with other pages? How long have you been experiencing these problems? How recent is the build? -- Chris Hoess
