John Duncan wrote:
John Duncan wrote:
Frank-Rainer Grahl wrote:
followup error from the above.
Is it? Seems unrelated to the aArguments error, but maybe I'm missing
something.
Should go away in a new build. Didn't look into it too hard but something was
not set because of the previous error.
- 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.
But I thought this error has persisted at least since 2.40, and the errors
above were only introduced in 2.50+
Sorry you are right. Do you use SeaTab X 2? I think its linked to it but not
sure.
Yep, using the latest 2.50a1 tinderbox build (Dec. 25, build 1482627108), all
errors in the browser portion seem to be fixed. The workaround for installing
addons seems to be working as well. It's styled a bit differently than on
older versions, but seems to be functional.
http://i.imgur.com/5NlCHGt.png
http://i.imgur.com/VmA47K8.png
Yes the notifications changed. The needed CSS changes to 'deflat' it and make
it more SeaMonkey friendly are not yet in.
_______________________________________________
support-seamonkey mailing list
[email protected]
https://lists.mozilla.org/listinfo/support-seamonkey
