Re: large list of files to send

2017-09-10 Thread Ray_Net 

Smiles wrote on 10-09-17 23:10:

good day

I have 120 photos, I can only zip 2 at a time to get under my isp 
limit of size
with out going to drop box is there a way of setting up email to send 
each one with the least amount of work


thanks
Smiles
I use http://www.uploadalbum.com/webalbum-download.php to create an 
album that I post on my webspace using filezilla.
Then I send the link of my online-albu to my friends and I ask them to 
send me the image-names they want.
then I send by mail the choiced images - instead of sending them all the 
120 photos.

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

Re: Image not printed

2017-09-10 Thread Ray_Net 

WaltS48 wrote on 11-09-17 01:24:

On 9/10/17 3:52 AM, Ray_Net wrote:

WaltS48 wrote on 10-09-17 02:41:

On 9/9/17 12:53 PM, Ray_Net wrote:

Paul in Houston, TX wrote on 09-09-17 02:41:

Ed Mullen wrote:
On 9/8/2017 at 12:04 AM, Paul in Houston, TX created this epitome 
of digital genius:

Paul B. Gallagher wrote:

Glen wrote:


David E. Ross wrote:

On 9/7/2017 1:25 PM, Ray_Net wrote:
On the printed page and on the print-preview screen the 
image is

not present... ...printing that page
 







Is this normal ?



By any chance, is it a background image?  If so:

1.  On the menu bar, go to [File > Page Setup].

2.  On the Format & Options tab of the Page Setup Window, 
make sure

the Print Background checkbox is checked.


I kept forgetting to look it up, as to the reason images were not
printing for me, and now it works again. Awesome! You saved me 
time.

Thank you! :)


Good for you, not for me. Changing the setting had no effect here.

There are lots of pages where SeaMonkey omits some of the 
content for

no reason I can
fathom. A good example is . Choose any
puzzle and try to print
it. You get the grid but no numbers -- totally useless.


SM 2.26.1:  I can print the sudoku ok but I cannot print the boxer
shorts pic from the
original url.  The pic actually comes from:
http://a248.e.akamai.net/f/248/9086/10h/origin-d4.scene7.com/is/image/Underarmour/V5ProdWithBadge?=on-model-mid|pdpZoomDesktop=0.50=jpg=85=sharp2=on,off=f0f0f0=0,0,1836,1950&$p_pos=450,380&$p_size=910,0=0,0,0,0&$p_src=is{Underarmour/V5-1277238-158_HTF} 




IE does not show any pics at all.


So the image is from a different site than the main site. Check 
Edit - Preferences -
Security - Images - and set the radio button for Load all images. 
See if that helps.


No change for me.  Already had it set to "all images". Toggled it 
and still the same.

Might help Ray though.


I had already (and I still use) "load all images" set.
I think that this option is to permit to see images in the Browser. 
The problem is that the image is visible on the screen of the 
Browser - so perfect ---> But the "print content" did not have the 
image. - so not perfect.

I just try to print with Internet Explorer ---> Same Problem !!!

Therefore my question is the same "Is this normal  ?"


For that site it probably is.

Did you notice the zoom feature when you move the mouse over an image?

Did you notice the images are links, not images coded in  tags 
in that web page?


Did you try opening the image link in a new tab and printing it?

I have no trouble opening an image link in a new tab and printing it.


Yes, me too, I noticed that also earlier ...but :
A page can be showed, but cannot be printed . this is strange ...



How do you print a link in a page? Not strange at all.



You rigth-click on the image then you use "Open link in New Window"
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Image not printed

2017-09-10 Thread WaltS48 

On 9/10/17 3:52 AM, Ray_Net wrote:

WaltS48 wrote on 10-09-17 02:41:

On 9/9/17 12:53 PM, Ray_Net wrote:

Paul in Houston, TX wrote on 09-09-17 02:41:

Ed Mullen wrote:
On 9/8/2017 at 12:04 AM, Paul in Houston, TX created this epitome 
of digital genius:

Paul B. Gallagher wrote:

Glen wrote:


David E. Ross wrote:

On 9/7/2017 1:25 PM, Ray_Net wrote:

On the printed page and on the print-preview screen the image is
not present... ...printing that page
 







Is this normal ?



By any chance, is it a background image?  If so:

1.  On the menu bar, go to [File > Page Setup].

2.  On the Format & Options tab of the Page Setup Window, make 
sure

the Print Background checkbox is checked.


I kept forgetting to look it up, as to the reason images were not
printing for me, and now it works again. Awesome! You saved me 
time.

Thank you! :)


Good for you, not for me. Changing the setting had no effect here.

There are lots of pages where SeaMonkey omits some of the content 
for

no reason I can
fathom. A good example is . Choose any
puzzle and try to print
it. You get the grid but no numbers -- totally useless.


SM 2.26.1:  I can print the sudoku ok but I cannot print the boxer
shorts pic from the
original url.  The pic actually comes from:
http://a248.e.akamai.net/f/248/9086/10h/origin-d4.scene7.com/is/image/Underarmour/V5ProdWithBadge?=on-model-mid|pdpZoomDesktop=0.50=jpg=85=sharp2=on,off=f0f0f0=0,0,1836,1950&$p_pos=450,380&$p_size=910,0=0,0,0,0&$p_src=is{Underarmour/V5-1277238-158_HTF} 




IE does not show any pics at all.


So the image is from a different site than the main site. Check 
Edit - Preferences -
Security - Images - and set the radio button for Load all images. 
See if that helps.


No change for me.  Already had it set to "all images". Toggled it 
and still the same.

Might help Ray though.


I had already (and I still use) "load all images" set.
I think that this option is to permit to see images in the Browser. 
The problem is that the image is visible on the screen of the Browser 
- so perfect ---> But the "print content" did not have the image. - 
so not perfect.

I just try to print with Internet Explorer ---> Same Problem !!!

Therefore my question is the same "Is this normal  ?"


For that site it probably is.

Did you notice the zoom feature when you move the mouse over an image?

Did you notice the images are links, not images coded in  tags in 
that web page?


Did you try opening the image link in a new tab and printing it?

I have no trouble opening an image link in a new tab and printing it.


Yes, me too, I noticed that also earlier ...but :
A page can be showed, but cannot be printed . this is strange ...



How do you print a link in a page? Not strange at all.


--
Go Bucs, Pitt, Steelers!
Coexist 
National Popular Vote 
Ubuntu 16.04 LTS - Unity Desktop
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Anyone have the akalla x64 SM 2.52b somewhere?

2017-09-10 Thread WaltS48 

On 9/10/17 11:04 AM, Frank-Rainer Grahl wrote:
I probably need to do a Fx Nightly again just to see what changed but 
this is all so much urgkkk for only fanboys to love. This is all rushed 
and I personally hope it backfires but even this would do SeaMonkey no 
good.


Do you really call Photon and Quantum development over version 55, 56 
and 57 nighties, and 57 betas rushed?


When I first saw Australis, I went wtf?, then working with it over a 
series of Nightlies, I learned how to customize and use it.


Sure about 500,000 users installed CTR, but what percentage of total 
Firefox users is that.


When I first saw Photon in Fx 55.0, I went wtf?, where did my Menu 
Button icons go!. Now working with Photon over a series of Nightlies 
I've learned how to customize and use it.


Do I like all the changes. Not really, but clicking the Library button 
and having access to Bookmarks, Pocket List, History, Synced Tabs, 
Screenshots and Downloads is nice.


Call me fanboy if you like. Somebody has to counter the doom and gloom 
of the whiners.


--
Go Bucs, Pitt, Steelers!
Coexist 
National Popular Vote 
Ubuntu 16.04 LTS - Unity Desktop
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: large list of files to send

2017-09-10 Thread Paul B. Gallagher 

Smiles wrote:


good day

I have 120 photos, I can only zip 2 at a time to get under my isp
limit of size with out going to drop box is there a way of setting up
email to send each one with the least amount of work


You can reduce the work by setting up a template. Create a message with 
the intended recipient and subject line, save as a template. Then to 
send, double-click the template, choose the first attachment, send, 
double-click the template, choose the second attachment, send, etc.


Still a big hassle, I do recommend Dropbox or similar, let your 
recipient download at his convenience.


If you have your own website, post them there and send your recipient 
the links. If they're confidential, password-protect the zip files and 
send him the password, then take them down as soon as he's done.


Another option is to use an image editing program to compress them -- 
within reason, of course. A reasonable amount of compression is 
invisible to all but the most expert eyes. Then you can get more than 
two under your ISP's limit.


--
War doesn't determine who's right, just who's left.
--
Paul B. Gallagher

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

large list of files to send

2017-09-10 Thread Smiles 

good day

I have 120 photos, I can only zip 2 at a time to get under my isp limit 
of size
with out going to drop box is there a way of setting up email to send 
each one with the least amount of work


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

Re: Anyone have the akalla x64 SM 2.52b somewhere?

2017-09-10 Thread Frank-Rainer Grahl 

> Right, I keep forgetting that the C++ download manager is being retired.

Gone in 2.52.

> Cool. I will try out 2.53 then, as there is a noticeable speed difference
> (especially javascript) between the current FF nightly and SM 2.48.

2.49.1 should be quite nice. Its my main browser for months now and very 
stable. I think the most polished and best release yet. Hope not too many new 
bugs pop up.


> If things do not go well with the 57 release, it really could be
> corporate suicide from Mozilla.

They still have a lot of money to burn. Market share in 5 to 6 months should 
show if it is a success. I have my doubts. If you p*ss off enough power users 
who recommend it to others not much left. "Normal" users will just continue 
using Chrome. They don't care about privacy and all the other things Mozilla 
is touting as achievements for 57.


Have fun
FRG

John Duncan wrote:

 > Download Manager e.g. needs a serious makeover before I would want it to
 > be released. This is more a case study since 2.52 :)
Right, I keep forgetting that the C++ download manager is being retired.
 > I am still on 2.53. Didn't check if DOMi and cZ still work but if not
 > they could surely being patched up. But Adblock+ and uBlock are both
 > broken.
Right, with those moving toward pure web-extensions, I suppose SM will need to 
land web-extension support to properly run their most recent versions.

 > We switched to ESR so that we have more time to prepare a release.
 > Unless 4 to 5 programmers pop up it is unlikely then we will return the
 > do releases from the release repo. After the 52 ESR branch is eol we
 > plan to switch to ESR 59 for 2.56.x. If nad when it comes to that is
 > still unsure if Mozilla continues to destroy the old codebase. We need
 > to port Web Extension support and e10s at least for later releases but
 > this is a huge task for such a small team.
Totally agree. That sounds like a relatively gargantuan undertaking for the 
tiny council/SM team.

 >
 > I am personally still at 2.53 / 56. Seems to be quite fast. 2.54 is
 > unusable right now. Uninstalled all Fx 56/57 betas and nightlies and
 > switched to esr 52 for testing only. I probably need to do a Fx Nightly
 > again just to see what changed but this is all so much urgkkk for only
 > fanboys to love. This is all rushed and I personally hope it backfires
 > but even this would do SeaMonkey no good.
Cool. I will try out 2.53 then, as there is a noticeable speed difference 
(especially javascript) between the current FF nightly and SM 2.48.
It all does seem extremely rushed and unprofessional; perhaps Mozilla has 
finally lost their way. I swear the only thing people on /r/Firefox talk about 
is the current Nightly icon change and other trivial and/or unimportant minor 
browser features (theming userChrome.css, etc.) If things do not go well with 
the 57 release, it really could be corporate suicide from Mozilla.

 >
 > Building 2.49.1 should atart soon. Everything has been checked in now. A
 > little late but we do what we can with the limited resourced at hand.
No rush. The fact that the team gets such a great deal done with so little 
resources is a considerable achievement.


-john

Frank-Rainer Grahl wrote:

Forgive me if I have misunderstood the meeting minutes, but since the

nightly

release channel will continue to support things like XUL overlays, legacy
extensions, webextension eperiments, etc. [0], why don't you continue to
ingest & build off of mozilla-central?


Nightlies will, of course be build. The list of bug which needs to be
fixed before a SeaMonkey 2.54 would be usable is quite long and I didn't
even file one or two for bookmark and other problems yet:

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

Download Manager e.g. needs a serious makeover before I would want it to
be released. This is more a case study since 2.52 :)


Is the plan to eventually switch back from ESR once bug fixes are

landed and

the API removal spree has subsided? Or will the API changes break more
essential SeaMonkey features as well? It seems as if DOM
Inspector/Lightning/Chatzilla all still seem to be working in current

2.54

builds, which is a good sign.


I am still on 2.53. Didn't check if DOMi and cZ still work but if not
they could surely being patched up. But Adblock+ and uBlock are both
broken.

We switched to ESR so that we have more time to prepare a release.
Unless 4 to 5 programmers pop up it is unlikely then we will return the
do releases from the release repo. After the 52 ESR branch is eol we
plan to switch to ESR 59 for 2.56.x. If nad when it comes to that is
still unsure if Mozilla continues to destroy the old codebase. We need
to port Web Extension support and e10s at least for later releases but
this is a huge task for such a small team.

I am personally still at 2.53 / 56. Seems to be quite fast. 2.54 is
unusable right now. Uninstalled all Fx 56/57 betas and nightlies and
switched to esr 52 for testing only. I probably

Re: Anyone have the akalla x64 SM 2.52b somewhere?

2017-09-10 Thread John Duncan 

> Download Manager e.g. needs a serious makeover before I would want it to
> be released. This is more a case study since 2.52 :)
Right, I keep forgetting that the C++ download manager is being retired.
> I am still on 2.53. Didn't check if DOMi and cZ still work but if not
> they could surely being patched up. But Adblock+ and uBlock are both
> broken.
Right, with those moving toward pure web-extensions, I suppose SM will 
need to land web-extension support to properly run their most recent 
versions.

> We switched to ESR so that we have more time to prepare a release.
> Unless 4 to 5 programmers pop up it is unlikely then we will return the
> do releases from the release repo. After the 52 ESR branch is eol we
> plan to switch to ESR 59 for 2.56.x. If nad when it comes to that is
> still unsure if Mozilla continues to destroy the old codebase. We need
> to port Web Extension support and e10s at least for later releases but
> this is a huge task for such a small team.
Totally agree. That sounds like a relatively gargantuan undertaking for 
the tiny council/SM team.

>
> I am personally still at 2.53 / 56. Seems to be quite fast. 2.54 is
> unusable right now. Uninstalled all Fx 56/57 betas and nightlies and
> switched to esr 52 for testing only. I probably need to do a Fx Nightly
> again just to see what changed but this is all so much urgkkk for only
> fanboys to love. This is all rushed and I personally hope it backfires
> but even this would do SeaMonkey no good.
Cool. I will try out 2.53 then, as there is a noticeable speed 
difference (especially javascript) between the current FF nightly and SM 
2.48.
It all does seem extremely rushed and unprofessional; perhaps Mozilla 
has finally lost their way. I swear the only thing people on /r/Firefox 
talk about is the current Nightly icon change and other trivial and/or 
unimportant minor browser features (theming userChrome.css, etc.) If 
things do not go well with the 57 release, it really could be corporate 
suicide from Mozilla.

>
> Building 2.49.1 should atart soon. Everything has been checked in now. A
> little late but we do what we can with the limited resourced at hand.
No rush. The fact that the team gets such a great deal done with so 
little resources is a considerable achievement.


-john

Frank-Rainer Grahl wrote:

Forgive me if I have misunderstood the meeting minutes, but since the

nightly

release channel will continue to support things like XUL overlays, legacy
extensions, webextension eperiments, etc. [0], why don't you continue to
ingest & build off of mozilla-central?


Nightlies will, of course be build. The list of bug which needs to be
fixed before a SeaMonkey 2.54 would be usable is quite long and I didn't
even file one or two for bookmark and other problems yet:

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

Download Manager e.g. needs a serious makeover before I would want it to
be released. This is more a case study since 2.52 :)


Is the plan to eventually switch back from ESR once bug fixes are

landed and

the API removal spree has subsided? Or will the API changes break more
essential SeaMonkey features as well? It seems as if DOM
Inspector/Lightning/Chatzilla all still seem to be working in current

2.54

builds, which is a good sign.


I am still on 2.53. Didn't check if DOMi and cZ still work but if not
they could surely being patched up. But Adblock+ and uBlock are both
broken.

We switched to ESR so that we have more time to prepare a release.
Unless 4 to 5 programmers pop up it is unlikely then we will return the
do releases from the release repo. After the 52 ESR branch is eol we
plan to switch to ESR 59 for 2.56.x. If nad when it comes to that is
still unsure if Mozilla continues to destroy the old codebase. We need
to port Web Extension support and e10s at least for later releases but
this is a huge task for such a small team.

I am personally still at 2.53 / 56. Seems to be quite fast. 2.54 is
unusable right now. Uninstalled all Fx 56/57 betas and nightlies and
switched to esr 52 for testing only. I probably need to do a Fx Nightly
again just to see what changed but this is all so much urgkkk for only
fanboys to love. This is all rushed and I personally hope it backfires
but even this would do SeaMonkey no good.

Building 2.49.1 should atart soon. Everything has been checked in now. A
little late but we do what we can with the limited resourced at hand.

FRG

John Duncan wrote:

Frank-Rainer Grahl wrote:

I have a pacthes up 2.54 but it still needs at least two bugs fixed
before I would call it usable.

I am using a 2.53 with a few fixes still in review applied. If you want
it shoot me a mail Can bake any platform but Linux i686.

FRG

TCW wrote:

On 9/7/2017 1:26 PM, S Slicer wrote:

TCW wrote:

Before l10n.mozilla-community.org went down, I had the 2.52b x64
akalla built but it seems to be corrupt. Tried google but nothing's
coming up. 2.51 is the newest I could fine. Anyone have the x64
2.52b build

Re: UseNet group message threading all messed up

2017-09-10 Thread Paul B. Gallagher 

Daniel wrote:


In one (and only one) of my UseNet groups, rec.arts.drwho, the
threading of all the old threads has become messed up, in that, when
I select a message, from an old thread, the message and header
displayed in the Message Pane can be something totally different to
that shown in the Threads Pane.

Selecting the next message in the Threads Pane can result in a
message from a totally different thread being displayed  even a
message from the last displayed Thread being displayed.

As I've got the number of Unread messages in the News Group down to
about 39,000 unread out of a total 177,000 posts, so I'm not wanting
to delete the index file and "start" anew, so has anybody got any
suggestions how I might reconstruct that index file without having
to start from scratch, 177,000 unread out of 177,000??


If the unread count were something more reasonable than 39,000, I'd 
suggest this, which has worked for me:


1) Select all, mark as read.

2) Change view settings to all messages, all threads, unthreaded, sorted 
by date.


3) Scroll to the new end of the list, select the last day (or whatever 
time corresponds to the period since you last read messages). Mark those 
as unread.


4) Restore view settings to all messages, threads with unread, threaded, 
sorted by date.


But with 39,000 unread messages, it seems unmanageable, at least for 
this speed reader. ;-)


Any chance you can restore an older version -- say, last week's -- of 
the index file from backup?


--
War doesn't determine who's right, just who's left.
--
Paul B. Gallagher
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Image not printed

2017-09-10 Thread Paul B. Gallagher 

David E. Ross wrote:


I think I have seen pages that could not be printed because the
owner had them composed that way on purpose.  This limits the ability
of others to capture and modify the page.  When I have seen this,
disabling JavaScript AFTER the page is fully loaded defeats the
blocking of printing.


Surely that isn't the case with websudoku.com, which has a "print" 
button for that specific purpose.


--
War doesn't determine who's right, just who's left.
--
Paul B. Gallagher

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

Re: SeaMonkey 2.48 Certificates

2017-09-10 Thread David E. Ross 
On 9/10/2017 2:03 AM, David Guymer wrote:
> Another site that SeaMonkey 2.48 won't let me gp tp is 
> https://www.seamonkey-project.org/start/
> 
> That version is rediculas tide up.
> 
> When will the next version be releast? I wonder if SeaMonkey 2.48 will 
> allow updates?
> 
> Very frustrated.
> 
> David Guymer
> 

gp??  tp??

-- 
David E. Ross


Yes, George Washington, Thomas Jefferson, and other
"founding fathers" owned slaves.  However, they created
a nation.  Robert E. Lee, Jefferson Davis, Thomas
"Stonewall" Jackson and other "heroes" of the
Confederacy tried to tear the nation apart.  Statues
and other monuments to those "heroes" of the
Confederacy actually celebrate traitors and treason.

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

Re: Image not printed

2017-09-10 Thread David E. Ross 
On 9/10/2017 12:52 AM, Ray_Net wrote:
> WaltS48 wrote on 10-09-17 02:41:
>> On 9/9/17 12:53 PM, Ray_Net wrote:
>>> Paul in Houston, TX wrote on 09-09-17 02:41:
 Ed Mullen wrote:
> On 9/8/2017 at 12:04 AM, Paul in Houston, TX created this epitome 
> of digital genius:
>> Paul B. Gallagher wrote:
>>> Glen wrote:
>>>
 David E. Ross wrote:
> On 9/7/2017 1:25 PM, Ray_Net wrote:
>> On the printed page and on the print-preview screen the image is
>> not present... ...printing that page
>> 
>>  
>>
>>
>>
>>
>>
>>
>> Is this normal ?
>>
>
> By any chance, is it a background image?  If so:
>
> 1.  On the menu bar, go to [File > Page Setup].
>
> 2.  On the Format & Options tab of the Page Setup Window, make 
> sure
> the Print Background checkbox is checked.
>
 I kept forgetting to look it up, as to the reason images were not
 printing for me, and now it works again. Awesome! You saved me 
 time.
 Thank you! :)
>>>
>>> Good for you, not for me. Changing the setting had no effect here.
>>>
>>> There are lots of pages where SeaMonkey omits some of the content 
>>> for
>>> no reason I can
>>> fathom. A good example is . Choose any
>>> puzzle and try to print
>>> it. You get the grid but no numbers -- totally useless.
>>
>> SM 2.26.1:  I can print the sudoku ok but I cannot print the boxer
>> shorts pic from the
>> original url.  The pic actually comes from:
>> http://a248.e.akamai.net/f/248/9086/10h/origin-d4.scene7.com/is/image/Underarmour/V5ProdWithBadge?=on-model-mid|pdpZoomDesktop=0.50=jpg=85=sharp2=on,off=f0f0f0=0,0,1836,1950&$p_pos=450,380&$p_size=910,0=0,0,0,0&$p_src=is{Underarmour/V5-1277238-158_HTF}
>>  
>>
>>
>>
>> IE does not show any pics at all.
>
> So the image is from a different site than the main site. Check 
> Edit - Preferences -
> Security - Images - and set the radio button for Load all images. 
> See if that helps.

 No change for me.  Already had it set to "all images". Toggled it 
 and still the same.
 Might help Ray though.

>>> I had already (and I still use) "load all images" set.
>>> I think that this option is to permit to see images in the Browser. 
>>> The problem is that the image is visible on the screen of the Browser 
>>> - so perfect ---> But the "print content" did not have the image. - 
>>> so not perfect.
>>> I just try to print with Internet Explorer ---> Same Problem !!!
>>>
>>> Therefore my question is the same "Is this normal  ?"
>>
>> For that site it probably is.
>>
>> Did you notice the zoom feature when you move the mouse over an image?
>>
>> Did you notice the images are links, not images coded in  tags in 
>> that web page?
>>
>> Did you try opening the image link in a new tab and printing it?
>>
>> I have no trouble opening an image link in a new tab and printing it.
>>
> Yes, me too, I noticed that also earlier ...but :
> A page can be showed, but cannot be printed . this is strange ...
> 

I think I have seen pages that could not be printed because the owner
had them composed that way on purpose.  This limits the ability of
others to capture and modify the page.  When I have seen this, disabling
JavaScript AFTER the page is fully loaded defeats the blocking of
printing.

-- 
David E. Ross


Yes, George Washington, Thomas Jefferson, and other
"founding fathers" owned slaves.  However, they created
a nation.  Robert E. Lee, Jefferson Davis, Thomas
"Stonewall" Jackson and other "heroes" of the
Confederacy tried to tear the nation apart.  Statues
and other monuments to those "heroes" of the
Confederacy actually celebrate traitors and treason.

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

Re: Anyone have the akalla x64 SM 2.52b somewhere?

2017-09-10 Thread Frank-Rainer Grahl 

> Forgive me if I have misunderstood the meeting minutes, but since the nightly
> release channel will continue to support things like XUL overlays, legacy
> extensions, webextension eperiments, etc. [0], why don't you continue to
> ingest & build off of mozilla-central?

Nightlies will, of course be build. The list of bug which needs to be fixed 
before a SeaMonkey 2.54 would be usable is quite long and I didn't even file 
one or two for bookmark and other problems yet:


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

Download Manager e.g. needs a serious makeover before I would want it to be 
released. This is more a case study since 2.52 :)


> Is the plan to eventually switch back from ESR once bug fixes are landed and
> the API removal spree has subsided? Or will the API changes break more
> essential SeaMonkey features as well? It seems as if DOM
> Inspector/Lightning/Chatzilla all still seem to be working in current 2.54
> builds, which is a good sign.

I am still on 2.53. Didn't check if DOMi and cZ still work but if not they 
could surely being patched up. But Adblock+ and uBlock are both broken.


We switched to ESR so that we have more time to prepare a release. Unless 4 to 
5 programmers pop up it is unlikely then we will return the do releases from 
the release repo. After the 52 ESR branch is eol we plan to switch to ESR 59 
for 2.56.x. If nad when it comes to that is still unsure if Mozilla continues 
to destroy the old codebase. We need to port Web Extension support and e10s at 
least for later releases but this is a huge task for such a small team.


I am personally still at 2.53 / 56. Seems to be quite fast. 2.54 is unusable 
right now. Uninstalled all Fx 56/57 betas and nightlies and switched to esr 52 
for testing only. I probably need to do a Fx Nightly again just to see what 
changed but this is all so much urgkkk for only fanboys to love. This is all 
rushed and I personally hope it backfires but even this would do SeaMonkey no 
good.


Building 2.49.1 should atart soon. Everything has been checked in now. A 
little late but we do what we can with the limited resourced at hand.


FRG

John Duncan wrote:

Frank-Rainer Grahl wrote:

I have a pacthes up 2.54 but it still needs at least two bugs fixed
before I would call it usable.

I am using a 2.53 with a few fixes still in review applied. If you want
it shoot me a mail Can bake any platform but Linux i686.

FRG

TCW wrote:

On 9/7/2017 1:26 PM, S Slicer wrote:

TCW wrote:

Before l10n.mozilla-community.org went down, I had the 2.52b x64
akalla built but it seems to be corrupt. Tried google but nothing's
coming up. 2.51 is the newest I could fine. Anyone have the x64
2.52b build handy?


I have 2.53a1, but this newsgroup would not let me attach it because
it is over 72 MG. I think is the last nightly build that I
downloaded.  The only other 64-bit one that I have saved is 2.45.


That's all right. I know *some* movement on getting it back on a
hosting place is happening
(https://bugzilla.mozilla.org/show_bug.cgi?id=1383642) but it might be
a while. I was already playing with the 2.54a builds but the amount of
stuff busted in it is forcing me to revert back.
Saw those patches for 2.54. Glad you guys are staying sane during the Mozilla 
API decimation.


Forgive me if I have misunderstood the meeting minutes, but since the nightly 
release channel will continue to support things like XUL overlays, legacy 
extensions, webextension eperiments, etc. [0], why don't you continue to 
ingest & build off of mozilla-central?


Is the plan to eventually switch back from ESR once bug fixes are landed and 
the API removal spree has subsided? Or will the API changes break more 
essential SeaMonkey features as well? It seems as if DOM 
Inspector/Lightning/Chatzilla all still seem to be working in current 2.54 
builds, which is a good sign.


Total removal of complete themes could be a larger issue, though.

Thanks for your continued support.

[0]: https://wiki.mozilla.org/Add-ons/Firefox57

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

Re: UseNet group message threading all messed up

2017-09-10 Thread WaltS48 

On 9/10/17 8:33 AM, Daniel wrote:
In one (and only one) of my UseNet groups, rec.arts.drwho, the threading 
of all the old threads has become messed up, in that, when I select a 
message, from an old thread, the message and header displayed in the 
Message Pane can be something totally different to that shown in the 
Threads Pane.


Selecting the next message in the Threads Pane can result in a message 
from a totally different thread being displayed  even a message from 
the last displayed Thread being displayed.


As I've got the number of Unread messages in the News Group down to 
about 39,000 unread out of a total 177,000 posts, so I'm not wanting to 
delete the index file and "start" anew, so has anybody got any 
suggestions how I might reconstruct that index file without having to 
start from scratch, 177,000 unread out of 177,000??




Select another newsgroup, select a message (read or unread), after it 
displays try the posts in re.arts.drwho again.


I see that problem occasionally in Mozilla groups and that fixes it for me.

--
Go Bucs, Pitt, Steelers!
Coexist 
National Popular Vote 
Ubuntu 16.04 LTS - Unity Desktop
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

UseNet group message threading all messed up

2017-09-10 Thread Daniel 
In one (and only one) of my UseNet groups, rec.arts.drwho, the threading 
of all the old threads has become messed up, in that, when I select a 
message, from an old thread, the message and header displayed in the 
Message Pane can be something totally different to that shown in the 
Threads Pane.


Selecting the next message in the Threads Pane can result in a message 
from a totally different thread being displayed  even a message from 
the last displayed Thread being displayed.


As I've got the number of Unread messages in the News Group down to 
about 39,000 unread out of a total 177,000 posts, so I'm not wanting to 
delete the index file and "start" anew, so has anybody got any 
suggestions how I might reconstruct that index file without having to 
start from scratch, 177,000 unread out of 177,000??


--
Daniel

User agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:51.0) Gecko/20100101 
SeaMonkey/2.48 Build identifier: 20170329183526

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

Re: SeaMonkey 2.48 Certificates

2017-09-10 Thread David Guymer 

Daniel wrote:

On 28/08/2017 1:26 AM, Lee wrote:

On 8/27/17, Daniel  wrote:

On 27/08/2017 2:17 PM, David Guymer wrote:

David Guymer wrote:

David E. Ross wrote:

On 8/26/2017 12:34 AM, David Guymer wrote:

There is something wrong with SeaMonkey 2.48.Every page I go to I
get
a
certificate warning.

I have aspersky Total Security 18.0. I have imported the Certificate
from this program with the same warning afterwards.

All other browswers are unaffected. News and mail are unaffected in
SeaMonkey.

David Guymer



Give us a link to an affected Web page, a page that does not
require a
login to an account that I do not have.



https://www.foxtel.com.au/my-account


Another important site that won't load is
https://my.gov.au/LoginServices/main/login?execution=e1s1

David Guymer


My SM 2.48 gets me to the my.gov.au "Secret Question" page  just
like it has done for years!!


Unless you've got Kaspersky installed on your machine & configured to
check all web traffic your situation is totally different.

see, for example,
https://bugs.chromium.org/p/project-zero/issues/detail?id=978
  Kasperky installs a WFP driver to intercept all outgoing HTTPS
connections. They effectively proxy SSL connections, inserting their
own certificate as a trusted authority in the system store and then
replace all leaf certificates on-the-fly. This is why if you examine a
certificate when using Kaspersky Antivirus, the issuer appears to be
"Kaspersky Anti-Virus Personal Root".

Lee


Ah!! No Kasperky, so Sorry for distracting you.

Daniel

Another site that SeaMonkey 2.48 won't let me gp tp is 
https://www.seamonkey-project.org/start/


That version is rediculas tide up.

When will the next version be releast? I wonder if SeaMonkey 2.48 will 
allow updates?


Very frustrated.

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

Re: Image not printed

2017-09-10 Thread Ray_Net 

WaltS48 wrote on 10-09-17 02:41:

On 9/9/17 12:53 PM, Ray_Net wrote:

Paul in Houston, TX wrote on 09-09-17 02:41:

Ed Mullen wrote:
On 9/8/2017 at 12:04 AM, Paul in Houston, TX created this epitome 
of digital genius:

Paul B. Gallagher wrote:

Glen wrote:


David E. Ross wrote:

On 9/7/2017 1:25 PM, Ray_Net wrote:

On the printed page and on the print-preview screen the image is
not present... ...printing that page
 







Is this normal ?



By any chance, is it a background image?  If so:

1.  On the menu bar, go to [File > Page Setup].

2.  On the Format & Options tab of the Page Setup Window, make 
sure

the Print Background checkbox is checked.


I kept forgetting to look it up, as to the reason images were not
printing for me, and now it works again. Awesome! You saved me 
time.

Thank you! :)


Good for you, not for me. Changing the setting had no effect here.

There are lots of pages where SeaMonkey omits some of the content 
for

no reason I can
fathom. A good example is . Choose any
puzzle and try to print
it. You get the grid but no numbers -- totally useless.


SM 2.26.1:  I can print the sudoku ok but I cannot print the boxer
shorts pic from the
original url.  The pic actually comes from:
http://a248.e.akamai.net/f/248/9086/10h/origin-d4.scene7.com/is/image/Underarmour/V5ProdWithBadge?=on-model-mid|pdpZoomDesktop=0.50=jpg=85=sharp2=on,off=f0f0f0=0,0,1836,1950&$p_pos=450,380&$p_size=910,0=0,0,0,0&$p_src=is{Underarmour/V5-1277238-158_HTF} 




IE does not show any pics at all.


So the image is from a different site than the main site. Check 
Edit - Preferences -
Security - Images - and set the radio button for Load all images. 
See if that helps.


No change for me.  Already had it set to "all images". Toggled it 
and still the same.

Might help Ray though.


I had already (and I still use) "load all images" set.
I think that this option is to permit to see images in the Browser. 
The problem is that the image is visible on the screen of the Browser 
- so perfect ---> But the "print content" did not have the image. - 
so not perfect.

I just try to print with Internet Explorer ---> Same Problem !!!

Therefore my question is the same "Is this normal  ?"


For that site it probably is.

Did you notice the zoom feature when you move the mouse over an image?

Did you notice the images are links, not images coded in  tags in 
that web page?


Did you try opening the image link in a new tab and printing it?

I have no trouble opening an image link in a new tab and printing it.


Yes, me too, I noticed that also earlier ...but :
A page can be showed, but cannot be printed . this is strange ...
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Anyone have the akalla x64 SM 2.52b somewhere?

2017-09-10 Thread John Duncan 

Frank-Rainer Grahl wrote:

I have a pacthes up 2.54 but it still needs at least two bugs fixed
before I would call it usable.

I am using a 2.53 with a few fixes still in review applied. If you want
it shoot me a mail Can bake any platform but Linux i686.

FRG

TCW wrote:

On 9/7/2017 1:26 PM, S Slicer wrote:

TCW wrote:

Before l10n.mozilla-community.org went down, I had the 2.52b x64
akalla built but it seems to be corrupt. Tried google but nothing's
coming up. 2.51 is the newest I could fine. Anyone have the x64
2.52b build handy?


I have 2.53a1, but this newsgroup would not let me attach it because
it is over 72 MG. I think is the last nightly build that I
downloaded.  The only other 64-bit one that I have saved is 2.45.


That's all right. I know *some* movement on getting it back on a
hosting place is happening
(https://bugzilla.mozilla.org/show_bug.cgi?id=1383642) but it might be
a while. I was already playing with the 2.54a builds but the amount of
stuff busted in it is forcing me to revert back.
Saw those patches for 2.54. Glad you guys are staying sane during the 
Mozilla API decimation.


Forgive me if I have misunderstood the meeting minutes, but since the 
nightly release channel will continue to support things like XUL 
overlays, legacy extensions, webextension eperiments, etc. [0], why 
don't you continue to ingest & build off of mozilla-central?


Is the plan to eventually switch back from ESR once bug fixes are landed 
and the API removal spree has subsided? Or will the API changes break 
more essential SeaMonkey features as well? It seems as if DOM 
Inspector/Lightning/Chatzilla all still seem to be working in current 
2.54 builds, which is a good sign.


Total removal of complete themes could be a larger issue, though.

Thanks for your continued support.

[0]: https://wiki.mozilla.org/Add-ons/Firefox57
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey