John Duncan wrote:
John Duncan wrote:
Frank-Rainer Grahl wrote:
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.
So I tested this out in safe mode (with all add-ons) disabled, and the
error seems to have disappeared. I will try going through each add-on
to determine which one is causing this 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.
No, I do not. This error (browsers[i] is undefined] still persists
even when I reboot into safe mode with all add-ons disabled, so I'm
thinking it's perhaps unrelated to extensions? Once again, I could be
wrong..
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.
Great. No worries; this is probably one of the nicest builds of SM
I've ever used!
the webaudio interface seems a bit glitched as well, but works if you
right click on it to play the content.
http://i.imgur.com/emcJad6.png
Okay, so both the webaudio and add-on install popup weirdness seem to be
caused by my theme. I switched to the default one, and while they're
still different than before (uglier imo, very modern/metro-y, not
OS-specific like they used to be. I'm assuming the default OS-specific
theme css has simply not been updated for these yet), they are at least
better than the way my current theme is handling them.
http://i.imgur.com/kM12F4o.jpg
http://i.imgur.com/opw5KLb.jpg
_______________________________________________
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey
