Created attachment 272815 [details] UserChrome.css file Gecko/200707100303 SeaMonkey/2.0a1pre I have a custom throbber setup for SeaMonkey. It consists of a single animated GIF file that looks just like the normal throbber image, but gets bigger and smaller. It alternates with the normal image. With 2.0a1, when I start SM, if the first thing I do is fetch a web page, then the throbber works OK for the rest of the process lifetime. But if the first thing I do is to go the mail window and read email, before reading any web page, then the throbber NEVER appears for the entire lifetime of that process. Any time the throbber should begin to throb, it simply disappears instead. When it should stop throbbing, the still image comes back. This all worked FINE in 1.5a, but has been a problem for several days now in 2.0a1 (I don't know when it started, but not before 2.0a1). I will attach my UserChrome.css file and the animated gif
Created attachment 272817 [details] animated GIF This is the Seamonkey animated throbber I use. (I got it from the web. Sorry, don't have an URL to give gredit)
Created attachment 272895 [details] userChrome.css The correct UserChrome.css file.
Attachment #272815 - Attachment is obsolete: true
Note: this is only an issue for users who, like myself, have their preferences set to start out displaying an blank page, rather than their home page or the last page visited. I choose to display a blank page to minimize startup time. A workaround for this bug is to change one's home page to "about:" and then display the home page on startup. This is essentially as fast as displaying a blank page on startup, but it does lose one's usual home page.
Does this still happen as the userChrome.css you have posted now gives a security error message. Denying for SM2.0a1
Flags: blocking-seamonkey2.0a1? → blocking-seamonkey2.0a1-
Created attachment 334191 [details] updated userChrome.css with more workarounds I have developed a new userChrome.css that works around numerous bugs. The attached version works around bug 355893, bug 382642, bug 388642 (this bug), and bug 428892. My original workaround for this bug was to change my browser so that it no longer started up with a blank page, but started up with a web page. That ensured the the throbber image appeared where it belongs. Since then, I've Changed userChrome.css to no longer refer to any chrome:// urls to work around bug 428892. That change seems to have also inadvertently worked around this bug. With this workaround in place, I find that I can have by browser configured to start up with a blank page, and the throbber still appears in the expected place. I believe this bug is now masked by bug 428892. If and when bug 428892 is fixed, and the workaround for it is no longer necessary, I suspect that this bug will re-emerge.
You need to log in before you can comment on or make changes to this bug.