Re: I hate tabs, but SM use it if more than one url is specified as the "home page"

[David E. Ross]

On 12/10/2016 12:01 PM, Ray_Net wrote:
> David E. Ross wrote on 10-12-16 18:53:
>> On 12/10/2016 8:19 AM, Ray_Net wrote:
>>> I work with SM without tabs, I prefer to have separate windows.
>>>
>>> I discovered recently that when starting SM - we can have 2 pages for
>>> the home page.
>>>
>>> I expected that those two pages will be each one on in a separate window.
>>>
>>> I have as the result that the two "home page" are in the same window
>>> with the use of 2 tabs.
>>>
>>> How can I do to have 2 windows instead of 2 tabs ?
>>>
>> 1.  On the SeaMonkey menu bar, select [Edit > Preferences].
>>
>> 2.  On the left side of the Preferences window, select [Browser > Link
>> Behavior].
>>
>> 3.  On the Link Behavior pane, set the various radio buttons to your
>> preferences.
>>
>> 4.  Select the OK button.
>>
> I have already done this a long time ago:
> - Link open behaviour - Open links meant to open a new windows in: [X]A 
> NEW WINDOW
> - When scripts want to open a new window: ("Don't divert custom windows 
> into tabs" is selected but all is greyed, so I cannot change it)
> - Links from other applications - Open links passed from other 
> applications in: [X]A NEW WINDOW
> 
> I think that's correct...
> But SM open a new tab for the second url on the "home page" instead of 
> opening a new window.
> 
> So, what could I do ? Filing a bug ?
> 

Did you save your multiple "home pages" while they were open as tabs?

-- 
David E. Ross

The Crimea is Putin's Sudetenland.
The Ukraine will be Putin's Czechoslovakia.
See .
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: akalla version 2.46 issues

[EE]

Mason83 wrote:

On 09/12/2016 20:10, EE wrote:


If I search in my URL bar, I get whatever engine is selected in the
searchbar.


https://bugzilla.mozilla.org/show_bug.cgi?id=1265881

It is less bother to change the search engine in the searchbar.  I have 
never bothered to do that from the Preferences.


___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Rebuilding SM Mail after a PC Failure

[EE]

Paul B. Gallagher wrote:

Henrik37 wrote:

Paul B. Gallagher wrote:

Henrik37 wrote:


...

I would like to recover my 'collected addresses' (which I think is the
address book) but I don't know what that file(s) named.


No, "collected addresses" is not /the/ address book. It's /an/ address
book that contains email name/address records that SM has picked up from
incoming and outgoing messages. Your true address book is "Personal
Address Book" at the top of the listing if you do CTRL-5.


...


If you are confident that your 2.39 profile is intact (undamaged by the
failure), I would recommend copying the entire profile. The format is
the same, so you don't have to worry about anything being corrupted or
misinterpreted by 2.40.

...


My new PC is running Win7-Pro.  The old PC was running XP-Pro.

The existing profile on the old PC has problems and I don't want to use
it in its entirety.

As you indicate, the names of the 'collected addresses' and the 'address
book' are the same.


"Different..."


What are the names of those two files?  I prefer to try and use the
approach outlined of pasting the recovered files into the new SM 2.40
as that approach has always worked for me in the past, at least with
mail messages.  With the two types of address files, I recognize that
it may not work but I want to try it as the mail messages have
already been pasted in and they work fine once SM 2.40 creates the
necessary .msf files.

Accordingly, I am back to the original problem:  what are the names
of the two address files and do these files have the same names in
v.2.39 from an XP machine and in v.2.40 in a Win7 machine?


As Felix Miata just noted downthread, you can find the answers at
.

abook.mab Personal address book [Window -> Address book -> Personal
Address Book]

history.mab Collected Address book [Window -> Address Book ->
Collected Addresses]

And much more, including instructions, if you follow the link.

File and folder /locations/ (not /names/) will be different, but you've
already said you know where to find your profile on both machines so you
should be good to go.

Why not just copy every file in the old profile with the extension .mab 
into to new profile?


___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: I hate tabs, but SM use it if more than one url is specified as the "home page"

[Ray_Net]

David E. Ross wrote on 10-12-16 18:53:

On 12/10/2016 8:19 AM, Ray_Net wrote:

I work with SM without tabs, I prefer to have separate windows.

I discovered recently that when starting SM - we can have 2 pages for
the home page.

I expected that those two pages will be each one on in a separate window.

I have as the result that the two "home page" are in the same window
with the use of 2 tabs.

How can I do to have 2 windows instead of 2 tabs ?


1.  On the SeaMonkey menu bar, select [Edit > Preferences].

2.  On the left side of the Preferences window, select [Browser > Link
Behavior].

3.  On the Link Behavior pane, set the various radio buttons to your
preferences.

4.  Select the OK button.


I have already done this a long time ago:
- Link open behaviour - Open links meant to open a new windows in: [X]A 
NEW WINDOW
- When scripts want to open a new window: ("Don't divert custom windows 
into tabs" is selected but all is greyed, so I cannot change it)
- Links from other applications - Open links passed from other 
applications in: [X]A NEW WINDOW


I think that's correct...
But SM open a new tab for the second url on the "home page" instead of 
opening a new window.


So, what could I do ? Filing a bug ?
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: I hate tabs, but SM use it if more than one url is specified as the "home page"

[David E. Ross]

On 12/10/2016 8:19 AM, Ray_Net wrote:
> I work with SM without tabs, I prefer to have separate windows.
> 
> I discovered recently that when starting SM - we can have 2 pages for 
> the home page.
> 
> I expected that those two pages will be each one on in a separate window.
> 
> I have as the result that the two "home page" are in the same window 
> with the use of 2 tabs.
> 
> How can I do to have 2 windows instead of 2 tabs ?
> 

1.  On the SeaMonkey menu bar, select [Edit > Preferences].

2.  On the left side of the Preferences window, select [Browser > Link
Behavior].

3.  On the Link Behavior pane, set the various radio buttons to your
preferences.

4.  Select the OK button.

-- 
David E. Ross

The Crimea is Putin's Sudetenland.
The Ukraine will be Putin's Czechoslovakia.
See .
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

I hate tabs, but SM use it if more than one url is specified as the "home page"

[Ray_Net]

I work with SM without tabs, I prefer to have separate windows.

I discovered recently that when starting SM - we can have 2 pages for 
the home page.


I expected that those two pages will be each one on in a separate window.

I have as the result that the two "home page" are in the same window 
with the use of 2 tabs.


How can I do to have 2 windows instead of 2 tabs ?
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: "J" instead of Outlook's happy face?

[Ray_Net]

Daniel wrote on 10-12-16 10:14:

On 10/12/2016 9:20 AM, Ray_Net wrote:

Paul B. Gallagher wrote on 09-12-16 22:16:

David E. Ross wrote:


It would be definitely wrong -- a major deviation from the commitment
to adhere to standards -- for any Mozilla-based application to
render 0x004A as anything other than J.


In an HTML page (or an HTML email), if the sender specifies the font
Wingdings and sends the character "J," SeaMonkey should do as it's
told and display the Wingdings glyph for that character point. That
wouldn't be a violation, would it?

The problem would arise, as I see it, if the recipient has set SM to
ignore the sender's font specification and use the recipient's
preferred font. For example, if you send me such a message and I've
forced Arial, I'll get a "J," and I'll have no one to blame but myself.

The OP might look under Edit | Preferences | Appearance | Fonts and
see whether "Allow documents to use other fonts" is checked. If not,
his own preferences will override those of the sender.


I have this option "Allow documents to use other fonts"set - so SM must
display the "J" in the windings font.


 providing, of course, you have wingdings font somewhere on your 
system!


Yes, I have it - BUT SM did not show me this "Character" ... in the 
correct font.

___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Meeting Notes

[David E. Ross]

On 12/10/2016 2:22 AM, Mason83 wrote:
> On 13/10/2016 17:31, Mason83 wrote:
> 
>> https://blog.mozilla.org/meeting-notes/ states:
>>
>>> If you are wondering why no new notes have been posted here
>>> for a long time, or if you want these postings to resume,
>>> see bug 1275636 and bug 1300427.
>>
>> https://bugzilla.mozilla.org/show_bug.cgi?id=1275636
>> "You are not authorized to access bug 1275636."
>>
>> That bug was opened on May 25, and seems to be marked
>> RESOLVED INVALID. Is it confidential by accident?
> 
> It is still impossible to view bug 1275636.
> 
> "You are not authorized to access bug 1275636."
> 
> Can someone fix that?
> 
> Regards.
> 

Bug #1275636 is cited in comment #2 of bug #1300427.  See
.  In that
comment, the "bug 1275636" is formatted as strike-out.

If I hover my cursor over the citation, the tool-tip says "RESOLVED
INVALID".  If I select the citation's link, however, I get:
> You are not authorized to access bug 1275636. To see this bug, you
> must first log in to an account with the appropriate permissions.
with "Access Denied" as the Web page's title.

So now we know #1275636 is resolved.  Why is it still "Access Denied"?

-- 
David E. Ross

The Crimea is Putin's Sudetenland.
The Ukraine will be Putin's Czechoslovakia.
See .
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Meeting Notes

[Mason83]

On 10/12/2016 15:20, WaltS48 wrote:
> On 12/10/2016 05:22 AM, Mason83 wrote:
>> On 13/10/2016 17:31, Mason83 wrote:
>>
>>> https://blog.mozilla.org/meeting-notes/ states:
>>>
 If you are wondering why no new notes have been posted here
 for a long time, or if you want these postings to resume,
 see bug 1275636 and bug 1300427.
>>> https://bugzilla.mozilla.org/show_bug.cgi?id=1275636
>>> "You are not authorized to access bug 1275636."
>>>
>>> That bug was opened on May 25, and seems to be marked
>>> RESOLVED INVALID. Is it confidential by accident?
>> It is still impossible to view bug 1275636.
>>
>> "You are not authorized to access bug 1275636."
>>
>> Can someone fix that?
>>
>> Regards.
>>
> 
> Bug 1300427 is still marked as
> 
> Status:
> UNCONFIRMED
> 
> So maybe that needs to be confirmed and fixed before bug 1275636 can be 
> revealed. Since access is denied, how do you know it seems to be marked 
> RESOLVED INVALID?

https://bugzilla.mozilla.org/show_bug.cgi?id=1300427#c2

> Anyway, if you are interested in reading the meeting notes for SeaMonkey 
> just bookmark 
> 
> I doubt that any meeting notes will be posted on the Mozilla blog ever 
> again. They have been missing since the end of April 2016.

I'll drop that page from my bookmarks, and use the one you provided.

Regards.

___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Meeting Notes

[WaltS48]

On 12/10/2016 05:22 AM, Mason83 wrote:

On 13/10/2016 17:31, Mason83 wrote:


https://blog.mozilla.org/meeting-notes/ states:


If you are wondering why no new notes have been posted here
for a long time, or if you want these postings to resume,
see bug 1275636 and bug 1300427.

https://bugzilla.mozilla.org/show_bug.cgi?id=1275636
"You are not authorized to access bug 1275636."

That bug was opened on May 25, and seems to be marked
RESOLVED INVALID. Is it confidential by accident?

It is still impossible to view bug 1275636.

"You are not authorized to access bug 1275636."

Can someone fix that?

Regards.



Bug 1300427 is still marked as

Status:
UNCONFIRMED

So maybe that needs to be confirmed and fixed before bug 1275636 can be 
revealed. Since access is denied, how do you know it seems to be marked 
RESOLVED INVALID?


Anyway, if you are interested in reading the meeting notes for SeaMonkey 
just bookmark 


I doubt that any meeting notes will be posted on the Mozilla blog ever 
again. They have been missing since the end of April 2016.


--
Visit Pittsburgh 
Coexist 
National Popular Vote 
Ubuntu 16.04LTS

___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: SM update status...

[Mason83]

On 10/12/2016 13:02, Richmond wrote:

> Mason83  writes:
> 
>> I'm not surprised you can't upgrade within SM, because you untarred
>> as root, but run as regular user. So SM doesn't have permission to
>> trash its installation folder.
> 
> Is it a security hazard if Seamonkey has access to change itself?

In Linux, binaries are typically owned by root, so regular users
can run them, but not change them (since they may be shared among
several users).

On a desktop system with a single user, it's not so important,
but I think it is good security practice.

Regards.

___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: SM update status...

[Richmond]

Mason83  writes:

> I'm not surprised you can't upgrade within SM, because you untarred
> as root, but run as regular user. So SM doesn't have permission to
> trash its installation folder.
>

Is it a security hazard if Seamonkey has access to change itself?
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: no plugins with current SM version

[Frank-Rainer Grahl]

Plans have not been finalized and its for the council to decide but I 
think yes, we will see a 2.49ESR.


Check the latest Status Meeting notes where this has been discussed:

https://wiki.mozilla.org/SeaMonkey/StatusMeetings/2016-12-06

FRG

Mason83 wrote:
 use Gecko Media Player

anymore next year, but such is life.


One should note that Firefox ESR 52 will retain support
for plug-ins.

Seamonkey devs: do you plan to base future Seamonkey releases
on the Forefox ESR or regular release?

Regards.



___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: no plugins with current SM version

[Mason83]

On 10/12/2016 11:16, Piscium wrote:
> On 9 December 2016 at 08:03, Mason83  wrote:
>> On 09/12/2016 08:21, Frank-Rainer Grahl wrote:
>>> Plugin support is discontined in Gecko / Firefox 52 which is the base of
>>> SeaMonkey. This was alrweady the case with 64 bit Windows versions for
>>> some time. Only Flash will work. All other plugings will no longer work.
>>> Nothing we / SeaMonkey devs can do about it.
>>>
>>> Binary Add-ons will stop working in SeaMonkey 2.50.
>>>
>>> Only normal add-ons will be supported at least until the end of 2017.
>>
>> References:
>>
>> https://blog.mozilla.org/futurereleases/2015/10/08/npapi-plugins-in-firefox/
>> https://blog.mozilla.org/futurereleases/2016/07/20/reducing-adobe-flash-usage-in-firefox/
>> https://www.fxsitecompat.com/en-CA/docs/2016/plug-in-support-has-been-dropped-other-than-flash/
>>
>> (npapi-eol) Remove support for all NPAPI plugins (except Flash)
>> https://bugzilla.mozilla.org/show_bug.cgi?id=1269807
> 
> Thanks Frank-Rainer and Mason for your help and references. I was not
> aware of that.
> 
> It is a pity that I won't be able to able to use Gecko Media Player
> anymore next year, but such is life.

One should note that Firefox ESR 52 will retain support
for plug-ins.

Seamonkey devs: do you plan to base future Seamonkey releases
on the Forefox ESR or regular release?

Regards.

___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Meeting Notes

[Frank-Rainer Grahl]

Sorry I don't have the rights to access the bug so can't tell you if it 
contains confidential/sensitive information.


If no one unmarks it it will stay confidential forever.

FRG

Mason83 wrote:

I believe that bug was marked as a security bug by mistake.
Can you access it? Is it really providing sensitive information?

It was reported in May 2016. How long before all bugs,
even security bugs are disclosed to the public?

Regards.


___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Meeting Notes

[Mason83]

I believe that bug was marked as a security bug by mistake.
Can you access it? Is it really providing sensitive information?

It was reported in May 2016. How long before all bugs,
even security bugs are disclosed to the public?

Regards.

On 10/12/2016 11:44, Frank-Rainer Grahl wrote:

> It is marked as a confidential security bug and so you can only view it 
> if you are on the cc list or have the appropriate rights.
> 
> FRG
> 
> Mason83 wrote:
>> On 13/10/2016 17:31, Mason83 wrote:
>>
>>> https://blog.mozilla.org/meeting-notes/ states:
>>>
 If you are wondering why no new notes have been posted here
 for a long time, or if you want these postings to resume,
 see bug 1275636 and bug 1300427.
>>>
>>> https://bugzilla.mozilla.org/show_bug.cgi?id=1275636
>>> "You are not authorized to access bug 1275636."
>>>
>>> That bug was opened on May 25, and seems to be marked
>>> RESOLVED INVALID. Is it confidential by accident?
>>
>> It is still impossible to view bug 1275636.
>>
>> "You are not authorized to access bug 1275636."
>>
>> Can someone fix that?
>>
>> Regards.

___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Meeting Notes

[Frank-Rainer Grahl]

> Can someone fix that?

It is marked as a confidential security bug and so you can only view it 
if you are on the cc list or have the appropriate rights.


FRG

Mason83 wrote:

On 13/10/2016 17:31, Mason83 wrote:


https://blog.mozilla.org/meeting-notes/ states:


If you are wondering why no new notes have been posted here
for a long time, or if you want these postings to resume,
see bug 1275636 and bug 1300427.


https://bugzilla.mozilla.org/show_bug.cgi?id=1275636
"You are not authorized to access bug 1275636."

That bug was opened on May 25, and seems to be marked
RESOLVED INVALID. Is it confidential by accident?


It is still impossible to view bug 1275636.

"You are not authorized to access bug 1275636."

Can someone fix that?

Regards.



___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Meeting Notes

[Mason83]

On 13/10/2016 17:31, Mason83 wrote:

> https://blog.mozilla.org/meeting-notes/ states:
> 
>> If you are wondering why no new notes have been posted here
>> for a long time, or if you want these postings to resume,
>> see bug 1275636 and bug 1300427.
> 
> https://bugzilla.mozilla.org/show_bug.cgi?id=1275636
> "You are not authorized to access bug 1275636."
> 
> That bug was opened on May 25, and seems to be marked
> RESOLVED INVALID. Is it confidential by accident?

It is still impossible to view bug 1275636.

"You are not authorized to access bug 1275636."

Can someone fix that?

Regards.

___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: no plugins with current SM version

[Piscium]

On 9 December 2016 at 08:03, Mason83  wrote:
> On 09/12/2016 08:21, Frank-Rainer Grahl wrote:
>> Plugin support is discontined in Gecko / Firefox 52 which is the base of
>> SeaMonkey. This was alrweady the case with 64 bit Windows versions for
>> some time. Only Flash will work. All other plugings will no longer work.
>> Nothing we / SeaMonkey devs can do about it.
>>
>> Binary Add-ons will stop working in SeaMonkey 2.50.
>>
>> Only normal add-ons will be supported at least until the end of 2017.
>
> References:
>
> https://blog.mozilla.org/futurereleases/2015/10/08/npapi-plugins-in-firefox/
> https://blog.mozilla.org/futurereleases/2016/07/20/reducing-adobe-flash-usage-in-firefox/
> https://www.fxsitecompat.com/en-CA/docs/2016/plug-in-support-has-been-dropped-other-than-flash/
>
> (npapi-eol) Remove support for all NPAPI plugins (except Flash)
> https://bugzilla.mozilla.org/show_bug.cgi?id=1269807

Thanks Frank-Rainer and Mason for your help and references. I was not
aware of that.

It is a pity that I won't be able to able to use Gecko Media Player
anymore next year, but such is life.
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: no plugins with current SM version

[Piscium]

On 9 December 2016 at 04:48, NoOp  wrote:

> How did you try akalla's 2.47? Try extracting to a ~/seamonkey folder
> and then ~/seamonkey/seamokey or from the folder: ./seamonkey

That is what I had done previously. Today I am trying a different
version, the one below, and so far it seems to work well.
https://archive.mozilla.org/pub/seamonkey/candidates/2.46-candidates/build6/linux-x86_64/en-US/seamonkey-2.46.tar.bz2

At work I use Windows (penance for my past sins and bad karma!). My
plan is on Monday to try the 2.46 Windows version.


> You can copy your gecko-mediaplayer files over to /usr/lib/mozilla/plugins

Instead of coping I created symlinks, and it seems to work well so far.

Thanks for your help.
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: "J" instead of Outlook's happy face?

[Daniel]

On 10/12/2016 9:20 AM, Ray_Net wrote:

Paul B. Gallagher wrote on 09-12-16 22:16:

David E. Ross wrote:


It would be definitely wrong -- a major deviation from the commitment
to adhere to standards -- for any Mozilla-based application to
render 0x004A as anything other than J.


In an HTML page (or an HTML email), if the sender specifies the font
Wingdings and sends the character "J," SeaMonkey should do as it's
told and display the Wingdings glyph for that character point. That
wouldn't be a violation, would it?

The problem would arise, as I see it, if the recipient has set SM to
ignore the sender's font specification and use the recipient's
preferred font. For example, if you send me such a message and I've
forced Arial, I'll get a "J," and I'll have no one to blame but myself.

The OP might look under Edit | Preferences | Appearance | Fonts and
see whether "Allow documents to use other fonts" is checked. If not,
his own preferences will override those of the sender.


I have this option "Allow documents to use other fonts"set - so SM must
display the "J" in the windings font.


 providing, of course, you have wingdings font somewhere on your system!

--
Daniel

User agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:43.0) Gecko/20100101 
SeaMonkey/2.40 Build identifier: 20160120202951

or
User agent: Mozilla/5.0 (X11; Linux x86_64; rv:41.0) Gecko/20100101 
SeaMonkey/2.38 Build identifier: 20150903203501

___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey