197843 - Major problems with alternate stylesheets and cache reload

Status: RESOLVED WORKSFORME

(SeaMonkey :: General, defect)

Description

[David Tenser [:djst]]

This bug is a weird one that seems to be very random, but is 100% reproducable
if you do it right.

I have tested this with 1.3 final, the latest nightly build, and the recent
nightlies in Phoenix, and all of them contains this bug but Phoenix behaves a
bit differently (and even more random).

Steps to reproduce:
1. Go to this exact url: http://texturizer.net/phoenix/
   (Do not go to http://texturizer.net/phoenix/index.html for example!)
2. In the square box in the bottom-right corner, there's a link to an
   alternate stylesheet called "Locked Menu". Click on that one.
3. Make sure you're now using the Locked Menu by hovering the mouse pointer
   over the menu to the left. A small link should appear, reading "Unlock
   Menu".
4. Hold the Shift key down all the time now, and press the Reload button on
   the toolbar. Wait until the page reloads and then press Reload again, while
   still having Shift pressed. Repeat this step a number of times.

Actual results: Sometimes, the page renders completely blank. Just the
background color gets rendered, everything else seems to be hidden. If you
right-click the blank document and select View Source, you will see the full
source of the page anyway. 

I'm not really sure if this is a JavaScript bug (since the alternate stylesheet
is loaded using JS) or if it's a rendering bug, therefore I'm filing this in
Browser-General.

Comment 1

[David Tenser [:djst]]

Attachment: Screenshot of how this bug can appear.

Btw, this bug is NOT reproducible in Phoenix 0.4 but it is in Phoenix 0.5 (so
the bug appeared somewhere between those build dates). I'll try to figure out
the exact date, if this bug is not confirmed until then.

Comment 2

[Jon Henry]

David, are you still able to reproduce this bug in recent Mozilla builds? I just
spent a while trying using yesterday's nightly trunk build and could not get it
to happen. Maybe something was fixed, either in the web site or Mozilla? Any new
information would be appreciated.

Comment 3

[David Tenser [:djst]]

Jon, thanks for reminding me of this bug. It seems to be fixed!