113021 - Simplest test case for proxy icon disappearing (favicon)

Status: RESOLVED EXPIRED

(SeaMonkey :: UI Design, defect)

Description

[John Morrison]

1) create a new profile (i.e., all default settings)
2) set the profile to open new windows with a blank
3) quit browser
4) _delete_ the cache folder
5) start browser and load http://cowtools/ 
    -- this will create the disk cache again with three entries: 
       one for the cowtools document, one for a gif in that page,
       and one (negative) for the cowtools/favicon.ico
6) shut down the browser
7) start browser (all the above was just to ensure that you were in an
   exactly known state before doing the next two steps).


8) Enter 'http://jrgm.mcom.com/' in the urlbar and hit enter
    -- this returns a simple HTML document, and (negatively) caches
       the jrgm/favicon.ico
9) Now, click on the link to index2.html in the current document
    -- proxy icon disappears and never returns for jrgm.mcom.com


This seems like something pretty fundamental is not quite right, since this 
is pretty much a base test case for favicon.

Comment 1

[Jeremy M. Dolan]

I have a very differant method to make the icon vanish in bug 111572.

It involves switching between two tabs, nothing to do with what's show as the
page is initially loaded.

Comment 2

[SineSwiper]

Everybody has a test case to make favicon disappear :)  Ranging from reloading
to apparent random behavior.  Is there some global solution that we are missing?

Comment 3

[Aleksey Nogin]

So far, all the "favicon disappear" problems that I have seen seen to indicate
that the favicons are not cached properly. I'll am currently trying to sort
trhough all the issues as see if there is indeed a common problem (or at least a
common solution).

Do you see anything unusual in about:cache while doing your 1-9? I often see
that they show up as expired for no good reason, but I still have to investigate
it in some thorough manner.

Comment 4

[Robert Kaiser]

MASS-CHANGE:
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614

Comment 5

[Robert Kaiser]

MASS-CHANGE:
This bug report is registered in the SeaMonkey product, but still has no comment since the inception of the SeaMonkey project 5 years ago.

Because of this, we're resolving the bug as EXPIRED.

If you still can reproduce the bug on SeaMonkey 2 or otherwise think it's still valid, please REOPEN it and if it is a platform or toolkit issue, move it to the according component.

Query tag for this change: EXPIRED-20100420