Desiree wrote:
On 9/30/2013 7:50 AM, EE wrote:
Desiree wrote:
On 9/22/2013 1:49 AM, Desiree wrote:
I just upgraded to 2.21 from 2.20 on Windows 8 Pro. I lost ALL mail
(already posted here about that).
SeaMonkey is minimized to the Taskbar and when I try to maximize it, it
behaves very weirdly. It shows the tabs in a vertical transparent list.
I can't maximize it.
It is COMPLETELY UNUSABLE AFTER MINIMIZING TO TASKBAR. It works
normally as long as I don't minimize it (or open Mail window as then I
cannot later go to SeaMonkey tabs window). Once minimized, it is
crippled. I don't know how to describe it. Is there a way to upload
screenshots here?
I'm really surprised no one here had the answer. I thought Mozilla read
this news group?
Someone joined dslreports.com just to answer this question that I had
posted there also. I use Fx 17.0.9 ESR as my default browser (but also
enjoy using SeaMonkey). Fx 17.0.9 ESR has this particular setting
defaulted to FALSE. But the latest SeaMonkey has it, for some
unfathomable reason, defaulted to TRUE. I suppose it must default to
"true" on Fx on some version past the current ESR version 17.0.9 and
SeaMonkey is just following Fx's lead. So, I assume I will also
encounter this absurdity on Fx 24 ESR when it is pushed through an
internal update in January 2014.
Anyhow, it is this setting "browser.taskbar.previews.enable" which has
changed from False to True in SM 2.21 and causes a horrible mess on
Windows 8 Pro. I toggled it back to False and instantly everything was
fine again. I cannot imagine why anyone would want to see a "preview"
of maybe 20 to 100 tabs on the taskbar. It is absurdities like this
that make me glad that with Fx ESR, I only have to endure changes ONCE a
year.
If you put settings like that into a user.js file, you never have to be
bothered with the settings being changed on you again.
How so? The DEFAULT behavior was changed so I don't follow your
reasoning. If I had a USER designated preference and I put that in a
user.js file then that wouldn't be changed with a new version of
SeaMonkey but this happened because the default behavior was changed.
Desiree, if you set a pref in a user.js file then, each time you start
SM or FF, that pref is applied *after* the prefs.js file is read, so,
unless the pref you set is totally disabled, SM/FF will start up with
the pref set to default and then be set as per your user.js file.
Or something like that!!
--
Daniel
User agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:21.0) Gecko/20100101
Firefox/21.0 SeaMonkey/2.18 Build identifier: 20130418192405
or
User agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101
Firefox/24.0 SeaMonkey/2.21 Build identifier: 20130827183508
_______________________________________________
support-seamonkey mailing list
[email protected]
https://lists.mozilla.org/listinfo/support-seamonkey
