312644 - website did not publish in Foxfire browser

Status: RESOLVED WORKSFORME

(Firefox :: General, defect)

Description

[leo]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.10) Gecko/20050716 Firefox/1.0.6
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.10) Gecko/20050716 Firefox/1.0.6

www.marksladestudio.com has periodic content changes.  The last change -
10.13.05 published in Explorer & Opera, but - as of 10.16.05 - did not publish
in Foxfire.  This has not happened before.  Please explain.  Thank you.

Reproducible: Always

Steps to Reproduce:
1.Go to Explorer - enter: www.marksladestudio.com
2.Go to Opera - enter: www.marksladestudio.com
3.Go to Foxfire - enter: www.marksladestudio.com

Actual Results:  
Explorer shows the published changes.
Opera shows the published changes.
Foxfire does not show the published changes.

Expected Results:  
We primarily use Foxfire as our browser.  Up until now, there hasn't been a
publishing problem with Foxfire.  Please let us know what should be done and if
it is a Mozilla/Foxfire problem.

Comment 1

[Jesse Ruderman]

The site looks the same to me in IE and Firefox.

Comment 2

[Jesse Ruderman]

I got these emails from the reporter:

======

Thank you for your reply.

As of 4:20 AM - Under the website heading "NEWS" -
This section has now published the text changes.
However, the LINK titled: "HERE" goes to the ORIGINALS
page where the new artwork has not published.

Under the heading site "ARTWORK" then "ORIGINALS" The
new artwork - Thumbnail titled: "ONE LIFE IN GARMISCH"
has not published. This can be checked against IE and
Opera.

Again, thank you very much for your attention to this.

=====

and

=====

The website has now fully published the changes in
Firefox.  Since it took four days, is there anything
we might do better?

Thanks again for your help.

=====

My guess is that Firefox had a cached copy of the page on your computer and for
some reason was displaying the cached copy instead of a new copy from the web
server.  I don't know why that would happen.  Unfortunately, I can't figure out
how to reproduce the bug given this report, so I can't figure out whether it was
due to a bug in Firefox or not.