Actually it *is* a SeaMonkey issue. This is caused by the file locale/
en-US/global/fontpackage.properties within en-US.jar which contains
the following lines:
# LOCALIZATION NOTE : (handled_languages): DONT_TRANSLATE
handled_languages=ja, ko, zh-tw, zh-cn
name_ja=Japanese Text Display
name_ko=Kor
Peter Potamus the Purple Hippo wrote:
> asmpgmr wrote:
> > Actually it *is* a SeaMonkey issue. This is caused by the file locale/
> > en-US/global/fontpackage.properties within en-US.jar which contains
> > the following lines:
> >
> > # LOCALIZATION NOTE : (h
Bob wrote:
> asmpgmr wrote:
> > Actually it *is* a SeaMonkey issue. This is caused by the file locale/
> > en-US/global/fontpackage.properties within en-US.jar which contains
> > the following lines:
> >
> > # LOCALIZATION NOTE : (handled_languages): DONT_TRANS
> On a previous occasion I did ask, but I got the impression from the
> negative reactions that even if I wrote a patch, it would be
> unceremoniously turned down.
>
Therein lies the problem. There seems to be somewhat of a lack of
regard for user choice on the part of the developers for things the
> > asmpgmr wrote:
> >> Out of curiosity, what is the problem that some of the developers have
> >> with modal dialogs anyway ?
>
> > They get in our way even in cases when you don't need them.
>
> To expand on that somewhat short statement: I think the
On Oct 24, 5:40 pm, Robert Kaiser wrote:
> 1) Tabs were not in IE until very recently (IE7) while Mozilla has had
> them for ages (Opera was the first tabbed browser, though).
>
> 2) The vast majority of users love tabs, please accept that while you
> might be one of our users, you are not the maj
On Oct 25, 8:14 am, Neil wrote:
> asmpgmr wrote:
> >Granted but why do things like change the download progress dialog UI to be
> >less usable
>
> As with the loss of the About dialog, this was fallout from the
> conversion from XPFE to Toolkit, which (surprise) has no p
On Oct 25, 10:02 am, Robert Kaiser wrote:
> Paul B. Gallagher wrote:
> > I think it's dysfunctional to have a download process complete silently
> > without telling me it succeeded, or worse yet, stall silently without
> > telling me there's a problem. I don't know when I can go open the file,
> >
On Oct 25, 10:37 am, Robert Kaiser wrote:
> asmpgmr wrote:
> > Well the tiny round buttons aren't good. I've never seen any app have
> > buttons like that, it needs normal buttons. Also what do you perceive
> > as wrong with the 1.x design ? It looks perfectly f
On Oct 25, 4:52 pm, Robert Kaiser wrote:
> asmpgmr wrote:
> > Now I realize this is subjective and that you think "progress dialogs
> > are soo backwards, only really old software uses such a thing".
>
> That's not what I think but you seem to be so convinced
The question still remains: are users who like the way things work in
SeaMonkey 1.x in the target audience for SeaMonkey 2.0 ?
As it stands I'm going to stick with SeaMonkey 1.1.x, for me there are
several show stoppers in SeaMonkey 2.0: awfulbar, extremely intrusive
infobars, bad password manager
On Oct 27, 5:36 am, Neil wrote:
> asmpgmr wrote:
> >Perhaps someone will take an old pre-alpha 1 build of SeaMonkey 2.0 which
> >supported early Gecko 1.9.1 before any of these UI changes were added, drop
> >in the current version of Gecko 1.9.1 and release that as a user
On Oct 28, 5:31 am, Robert Kaiser wrote:
> asmpgmr wrote:
> > Isn't there an early build out there that supports Gecko 1.9.1.x but
> > still has the SeaMonkey 1.1.x UI ?
>
> Not one that is nearly secure. And btw, now that we have a newer
> release, 1.1.18 is badly
On Oct 28, 3:05 pm, Robert Kaiser wrote:
> asmpgmr wrote:
> > On Oct 28, 5:31 am, Robert Kaiser wrote:
> >> asmpgmr wrote:
> >>> Isn't there an early build out there that supports Gecko 1.9.1.x but
> >>> still has the SeaMonkey 1.1.x UI ?
>
>
On Oct 28, 4:26 pm, Robert Kaiser wrote:
> asmpgmr wrote:
> > I've used Mozilla Suite/SeaMonkey 1.x for awhile and never once had a
> > security problem so I'm really not concerned about this.
>
> I've never seen that volcano spit fire, so it surely must be p
FYI - the removal of the form manager is a result of the migration
from the original wallet code to the newer satchel code. The form
manager was actually part of the password manager so if the 1.x form
manager could be ported to 2.0 then theoretically the original
password manager could be restored
Netscape 5 would have been an update to the Netscape Communicator
code, it was canceled in favor of a new rendering engine NGLayout
which became Gecko. Netscape 6 was unfortunately based upon an alpha
release of Mozilla Suite which was still in development.
http://en.wikipedia.org/wiki/Netscape_5
Saved forms data is in .w
Saved password data is in .s
More info about files in the profile directory:
http://kb.mozillazine.org/Profile_folder_-_SeaMonkey
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lis
Possible reversion - the site https://www.wellsfargo.com/ does not
display the password field in 1.1.14. This works fine in SeaMonkey
1.1.12
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-
I'm not running any extensions. Also I'm running Windows.
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey
Bug filed -
https://bugzilla.mozilla.org/show_bug.cgi?id=470050
May be the same as an old closed bug -
https://bugzilla.mozilla.org/show_bug.cgi?id=387971
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/li
> After updating to 1.1.14, when I go to www.wellsfargo.com, the line for
> the password entry box is gone! This has never happened with prior
> versions. Any suggestions?
There is nothing in 1.1.14 that makes it worth the hassle, go back to
1.1.13 which doesn't have the problem.
___
Peter Potamus the Purple Hippo wrote:
> NoOp wrote:
> > On 12/23/2008 04:39 AM, Robert Kaiser wrote:
> >> ST wrote:
> >>> Hello,
> >>>
> >>> After updating to 1.1.14, when I go to www.wellsfargo.com, the line for
> >>> the password entry box is gone! This has never happened with prior
> >>> versi
NoOp wrote:
> On 12/23/2008 10:45 AM, asmpgmr wrote:
> >
> > Peter Potamus the Purple Hippo wrote:
> >> NoOp wrote:
> >> > On 12/23/2008 04:39 AM, Robert Kaiser wrote:
> >> >> ST wrote:
> >> >>> Hello,
> >> >&g
Robert Kaiser wrote:
> John Doue wrote:
> > Robert Kaiser wrote:
> >> ST wrote:
> >>> Hello,
> >>>
> >>> After updating to 1.1.14, when I go to www.wellsfargo.com, the line for
> >>> the password entry box is gone! This has never happened with prior
> >>> versions. Any suggestions?
> >>
> >> This
25 matches
Mail list logo
