User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:188.8.131.52) Gecko/20091221 Gentoo SeaMonkey/2.0.1 Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:184.108.40.206) Gecko/20091221 Gentoo SeaMonkey/2.0.1 After migrating a profile used by Seamonkey 1.1, I ave noticed multiple problems that occur while using that profile and not a newly created Seamonkey 2 profile. Specific problems: Stylesheets are not loaded correctly on some pages. Examples: http://www.crutchfield.com/index.html, http://www.freescale.com/webapp/sps/site/homepage.jsp?nodeId=0162468636. Other pages on these sites DO work correctly however. Logging into TD Bank online banking does not work. It displays a "Sorry, the information you entered is incorrect" message, even when using a valid account. The message is formatted differently from the real error message that a non-broken profile shows, which could be the same stylesheet problem. Clicking on the throbber takes you to chrome://navigator-region/locale/region.properties instead of the seamonkey project homepage. The "account central" view in mailnews displays the contents of chrome://messenger/locale/messenger.properties Address books are all named "chrome://messenger/locale/messenger.properties" and cannot be renamed. Reproducible: Always Steps to Reproduce: 1. Install Seamonkey 2 2. Migrate a profile used by seamonkey 1.1 Actual Results: Functionality noted above does not work correctly.
We can't do much unless you attach the profile(s) and/or narrow down what is wrongly migrated.
Version: unspecified → SeaMonkey 2.0 Branch
Started investigating this more, it seems several preferences get set to chrome://.../.../....properties URLs instead of the actual strings (all throbber URL prefs, ldap/address book settings, mailnews.account_central_page.url)... even some prefs that are supposed to be boolean values. I haven't figured out what's causing some stylesheets to not load or some forms to post with empty bodies yet.
Closing as INCOMPLETE (and SeaMonkey 2.1 is now in Beta2)
Status: UNCONFIRMED → RESOLVED
Last Resolved: 7 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.