JTK <[EMAIL PROTECTED]> wrote in
[EMAIL PROTECTED]">news:[EMAIL PROTECTED], on 30 Dec 2001: 

> Excuse me?  On this issue alone, to date I've:
> 
> - Exposed the problem and brought it to the attention of the
> Mozilla "community".

No, you've bitched and moaned

> - Explained the single step necessary to duplicate it.

Which is?  I've followed everything you've posted on Windows 2000 and 
Linux and see nothing wrong

> - Proven it's not Proxomitron.

I have tried with and without Proxomitron.  My linux machine gets it's 
connection from my 2k machine.  The routing software I use is set to go 
through Proxomitron for it's access, so I can't reproduce with or 
without it on Win 2k or Linux

> - Proven it's not Windows 2000 (==IE and NC4.7x work fine).

You have "proven" nothing

> - Proven it is Mozilla.

Proven it's user error, more than anything.  If it were Mozilla and you 
posted steps to reproduce it, I would be able to do it on at least one 
of the builds I have.  My Win 2k machine has a CVS optimized build, a 
Debug build, a relatively recent nightly, and the latest milestone (at 
this time, that would be .9.7).  My linux machine has a new nightly and 
.9.7.  None show any problems like you are having

> - Come up with a few hypotheses as to what the source of the defect
> in Mozilla may be.

Which are?  You keep saying Mozilla has a broken cache, but you have 
posted NOTHING showing any evidence of this.  If you'd maybe get 
yourself a debugger and step through Mozilla during the page load, and 
see that it doesn't check the expiration date on the cached page before 
loading it, then you would have a perfectly valid argument.  If you'd 
post a way to reproduce this, you would have an arguement.  CNN.com says 
right now:
Updated: 12:40 a.m. EST (0540 GMT) -- 31 December 2001
Wow, how about that, it has the right date and everything.  Quite 
amazing, really.  

As an after thought, perhaps you should try deleting \cache.  You don't 
seem to ever clean out your profile between builds, so perhaps your 
cache is screwed up because of the cache structure changing throughout 
the course of the project and your system is having some problems 
adjusting.  Maybe try a new profile to clear out old prefs that could be 
messing things up.  Never tried that, did you?  And you won't either, 
will you?

-- 
ICQ: N/A (temporarily)
AIM: FlyersR1 9
email: [EMAIL PROTECTED]
_ = m

Reply via email to