I upgraded from 0.9.3 to 2001091003 (by way of the previous nightly build for 0.9.4), and the mail/news icons (get message, new message, etc) look like they are from the classic theme, and are not positoned correctly. The icons in the folder subwindow and the message icons are also from classic. I have not verified this bug (by reinstalling 0.9.3 and upgrading twice) I have had the profile around since 0.9.2....

WFM Win98SE build 2001091103 Reporter: Close Mozilla and in your profile directory delete the /chrome/ directory and then restart Mozilla. Do NOT delete any OTHER /chrome/ directory in any directory other than your profile.

That took care of it. Is that standard procedure for an upgrade? Removing chrome directory also removed the non-standard chromes i'd downloaded. (But they stank anyway, so oh well) Evan

I rebooted, and the chrome regressed to partial modern / partial classic mode... I quit mozilla, and quit turbo (the little icon in the taskbar/watchamacallit), and deleted the chrome folder again, and restarted mozilla. this time it's *all* classic. I changed it to modern, and restarted mozilla. Now it is all modern. Rebooted again, and all is well. I'm reopening it to get these notes noticed. Please let me know if that's not the right thing to do...

I'm seeing this too, using recent branch builds on win98. nominating for nsbranch

Just to confirm that I am seeing this behavior too on Windows 2000. I can't say about Linux as I've not got this build yet. I'll get it in a couple of days and get back to you.

cc'ing ben for possible classic skin problem.

this is a chrome registry problem. It seems that the messenger skin component from classic is being used instead of the modern one. This seems to happen sometimes when you install one build over an old build. Hyatt probably has a better idea than me of how to fix this.

I believe this has been unnecessarily blamed on turbo. I see this frequently without turbo; so do many others, on and off.

Removing turbo markings until someone shows that this is a specific problem that only happens in turbo mode.

*** This bug has been marked as a duplicate of 97749 ***