User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:2.0b12pre) Gecko/20110208 Firefox/4.0b12pre SeaMonkey/2.1b3pre Build Identifier: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:2.0b12pre) Gecko/20110208 Firefox/4.0b12pre SeaMonkey/2.1b3pre Known Issues for FF4b11 that are also present in SM2.1b2: All Systems: * The site Formspring is not displaying content to beta users due to bad "user-agent" detection in their code (see bug 620344) Mac OS X: * The 32bit Microsoft Silverlight plugin fails to load when using a 64bit version of Firefox on Mac OS X 10.6. Sites that depend on the plugin (such as Netflix) will fail to work (see bug 598406) This version of the beta will not work on Macintosh hardware with Power PC CPUs (see bug 587799) * This version of the beta will not work on Macintosh hardware with Power PC CPUs (see bug 587799) Linux and Unix: * The video control buttons may not work when viewing QuickTime videos with libtotem (see bug 625036) * Users compiling from source might need a newer gcc and libstdc++ as the build requirements have changed (see bug 578880) Reproducible: Always

> Mac OS X: > > * The 32bit Microsoft Silverlight plugin fails to load when using a 64bit > version of Firefox on Mac OS X 10.6. Sites that depend on the plugin (such as > Netflix) will fail to work (see bug 598406) This version of the beta will not > work on Macintosh hardware with Power PC CPUs (see bug 587799) This is because we will fail to run any 32-bit plugin using carbon based NPAPI on 64-bit 10.6. This needs to be mentioned in the release notes. The work-around is to offer a re-start in 32-bit mode which was implemented for Firefox in bug 628651. Since we don't have that, we should mention that users can restart SM in 32-bit mode (and how to do that).

Callek pointed out hours ago that this is also to be included albeit with different wording. I just spaced adding it after I submitted this bug for him. * Users using Firefox Sync with their mobile device will need to update to the latest Firefox 4 beta for mobile

Moving stefanh's bug 631282 comment 4 here: "I think you should add bug 626096 to the known issues. I talked to KaiRo about this yesterday, and he suggested adding that to the release notes." To which I replied: "That bug points at bug 622542 which landed today. I think we should wait and see whether the final b2 Mac build still has the issue and then decide." @stefanh: AFAICS b2 Mac builds are already available on FTP. Can you give it a spin? And if it turns out to still be an issue, maybe also provide me with a statement that I can copy&paste 1:1 to the release notes so I make no mistake? Thanks!

Neil replied to KaiRo in m.d.a.seamonkey: "> don't trust it with any non-backed-up data (note that it will re-use your 2.0.x profiles). In particular it will upgrade your history to a format incompatible with 2.0.x and if you try to go back then 2.0.x will rename your history to places.sqlite.corrupt and create a new one."

(In reply to comment #3) > @stefanh: AFAICS b2 Mac builds are already available on FTP. Can you give it a > spin? And if it turns out to still be an issue, maybe also provide me with a > statement that I can copy&paste 1:1 to the release notes so I make no mistake? > Thanks! It's still an issue in the b2 build. Something like this should suffice - note that this is not an c&p, you might need to re-phrase it: "When hardware acceleration is off, background-colors in the ui (toolbar, status bar etc) might not update correctly when you switch focus from/to a window. Users running Macs with certain older hardware (like the Intel GMA950 chipset) will experience this even if they haven't turned off hardware acceleration in preferences." The last part is there because very few people know what hw acc is and it seems that even though you have it on by default it's off if the graphics can't handle it (and I know the integrated graphics in GMA950 don't handle it since I have it in my mini)

(In reply to comment #1) > we should mention that users can restart SM in 32-bit mode (and how to do that). @stefanh, can you elaborate on that? The rest of us has no Mac, so either someone with a Mac comes up with something worth citing or I'll have to skip the details. Things I'll add with URLs transformed to "(see bug xxx)", unless (welcome!) feedback indicates otherwise: Data loss warning: If you use a profile with this beta or any later version and then try to go back to SeaMonkey 2.0, SeaMonkey will rename your history file to places.sqlite.corrupt and create a new places.sqlite file, effectively resetting your browsing history. This is because the internal format changed and the upgrade process only works in one direction. https://bugzilla.mozilla.org/show_bug.cgi?id=615950 SeaMonkey Sync UI does not fully match Firefox Sync UI yet, but both are using the same back-end. To use a Sync account with multiple devices you need to make sure all of them use the latest version of Sync (i.e. always use the latest beta of SeaMonkey 2.1 or Firefox 4, desktop and mobile). http://code.google.com/p/fbug/issues/detail?id=4086 After installing the latest Firebug 1.7 pre-release and restarting the application, the Navigation Toolbar will only contain the Firebug button and otherwise be empty. https://bugzilla.mozilla.org/show_bug.cgi?id=626096 Mac: When hardware acceleration is off, background colors in the UI (toolbar, status bar etc.) might not update correctly when you switch focus from/to a window. Users running Macs with certain older hardware (like the Intel GMA950 chipset) will experience this even if they haven't turned off hardware acceleration in Preferences (Appearance/Content). https://bugzilla.mozilla.org/show_bug.cgi?id=598406 Mac: The 32-bit Microsoft Silverlight plugin fails to load when using a 64-bit version of SeaMonkey on Mac OS X 10.6. Sites that depend on the plugin (such as Netflix) will fail to work. You will need to restart in 32-bit mode. https://bugzilla.mozilla.org/show_bug.cgi?id=625036 Linux: The video control buttons may not work when viewing QuickTime videos with libtotem. https://bugzilla.mozilla.org/show_bug.cgi?id=578880 Linux: Users compiling from source might need a newer gcc and libstdc++ as the build requirements have changed.

(In reply to comment #6) > (In reply to comment #1) > > we should mention that users can restart SM in 32-bit mode (and how to do that). > > @stefanh, can you elaborate on that? Sure, how about: ---------------------------------------- To set SeaMonkey to start in 32-bit mode: 1) Make sure SeaMonkey is not running 2) In your Applications folder, right-click (or Control-click) the SeaMonkey application icon and choose "Get Info". 3) In the panel, select "Open in 32-bit mode" SeaMonkey will now always start in 32-bit mode. ---------------------------------------- (assuming that it's clear on how to revert the behaviour) > > https://bugzilla.mozilla.org/show_bug.cgi?id=626096 > Mac: When hardware acceleration is off, background colors in the UI (toolbar, > status bar etc.) might not update correctly when you switch focus from/to a > window. Users running Macs with certain older hardware (like the Intel > GMA950 chipset) I'm actually a bit unsure whether "chipset" in "GMA950 chipset" is correct. Looking at http://en.wikipedia.org/wiki/Intel_GMA, I think "graphics processor" is more correct.

(And it should probably read "GMA 950")

Checking in index.en.html; /www/seamonkeyproject-org/src/releases/seamonkey2.1b2/index.en.html,v <-- index.en.html new revision: 1.4; previous revision: 1.3 done