John Duncan wrote:
2.50 seems to be running much better than 2.46 release, from what I can tell.
Try 2.49a2 instead. It will be the next ESR release and probably will become
the standard release till 2018. Worst case it might also be the last one if
the XUL and XPI deprecation goes thru as planned.
There are a couple issues with 2.50 thus far, but they seem negligible:
- When you load a web page in a new tab, there is a type error:
Error: TypeError: aArguments is undefined.
Source File: chrome://navigator/content/tabbrowser.xml
Already fixed.
The given line is: ``aArguments.unshift(aBrowser);"
(line 419)
- When you open Mailnews, there is a syntax error in the 'messengerdnd.js' file
Error: SyntaxError: expected expression, got ')'
Source File: chrome://messenger/content/messengerdnd.js
Already fixed.
The given line is: ``else if (types.includes("text/x-moz-url")))"
(line 242)
- When you open Mailnews, there is a syntax error in the 'tabmail.xml' file
Error: TypeError: tabinfo is undefined
Source File: chrome://messenger/content/tabmail.xml
The given line is: ``let browserFunc = tabInfo.mode.getBrowser ||
tabInfo.mode.tabType.getBrowser;"
(line 779)
followup error from the above.
- This has been an issue for awhile, but any time you click on an email or
news message in mailnews, there is a type error in the 'tabbrowser.xml' file
Error: TypeError: browsers[i] is undefined
Source File: chrome://navigator/content/tabbrowser.xml
The given line is: ``if (browsers[i].contentDocument == aDocument)"
(line 350)
followup error from the above.
- Installing add-ons from a .xpi file seems broken (updating from inside of
about:addons or installing manually from a file still seems to work; it's just
broken when you click on a .xpi file inside of the browser and the urlbar
popup menu comes up broken)
Here is a picture of what I am referring to: http://i.imgur.com/pjZn9fp.png
Not 100% fixed right now but a workaround is in. Works in current builds.
- 2.46 had a regression wherein, when you viewed a large/tall image unscaled
(by opening it in its own tab and clicking on it), portions of the top of it
would become cut off as you scrolled up (it never lets you reach the top of
the image). This is the same in 2.50.
I tested this bug with this image: http://i.imgur.com/c1NOLaN.png
Probably a Gecko rendering bug. You should report it against Core. Maybe
Layout Images. If not right someone will move it to the correct component.
FRG
_______________________________________________
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey