Re: WYSIWYG printing?

[Paul B. Gallagher]

Ray_Net wrote:


I think that what http://www.nytimes.com do is perfect ...We need to
print only the text saving the forest 


The story I cited as an example has a very useful graphic showing the 
range of North Korean missiles. How can I include that when I print the 
page?


--
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: Unable to add a new mail account in SM 2.46 under Windows 10

[Ray_Net]

WaltS48 wrote on 06-03-17 19:47:

On 03/06/2017 11:27 AM, Alex Beauroy wrote:

Hi there!!!
I went to Mail & newsgroup account settings via the Edit menu
then to : add account
but the account wizard freezes to the pop up window :"Incoming Server 
Information" suggesting a newsgroup server

I just wanted to add an e-mail account!!!
What should I do
Thanks in advance for your assistance
Best Regards
@lex




  * After creating a news account through clicking a news URL, the
MailNews account wizard may be broken (the account type will
always be News). To work around the problem, set the
mail.server.serverX.valid pref (where X is the internal number of
the corresponding news account) to true in about:config, or delete
the invalid news account (bug 521861
).




Any idea WHEN this bug 
https://bugzilla.mozilla.org/show_bug.cgi?id=521861 will be corrected ?

(Reported: 8 years ago)
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: WYSIWYG printing?

[Ray_Net]

Paul B. Gallagher wrote on 05-03-17 07:02:
Many website nowadays have their own "Print" buttons that deliver what 
the designers consider "printer-friendly" versions of their pages. But 
even if I ignore those and use SeaMonkey's own "Print" function, many 
sites outsmart me by serving their "printer-friendly" versions. A 
prime example is . Pick any page and print it, 
and you'll find that you've lost all the graphics, fonts, and layout 
and gotten only a plain-text version of the page.


Does anyone know how to outsmart these sites and print the pages as 
received, complete with all the bells and whistles?


Conversely, for pages that are too fancy/fussy for my taste and don't 
serve dumbed-down versions on their own, is there a way for the user 
to select that?


Thanks.

I think that what http://www.nytimes.com do is perfect ...We need to 
print only the text saving the forest 

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

Re: Unable to add a new mail account in SM 2.46 under Windows 10

[WaltS48]

On 03/06/2017 11:27 AM, Alex Beauroy wrote:

Hi there!!!
I went to Mail & newsgroup account settings via the Edit menu
then to : add account
but the account wizard freezes to the pop up window :"Incoming Server 
Information" suggesting a newsgroup server

I just wanted to add an e-mail account!!!
What should I do
Thanks in advance for your assistance
Best Regards
@lex




  * After creating a news account through clicking a news URL, the
MailNews account wizard may be broken (the account type will
always be News). To work around the problem, set the
mail.server.serverX.valid pref (where X is the internal number of
the corresponding news account) to true in about:config, or delete
the invalid news account (bug 521861
).




--
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: Fastmail and SeaMonkey

[Alexander Yudenitsch]

Hi, NFN Smith! Thanks for writing, on 06 Mar 17 13:49:

I decided to reply below the quote, instead of the 
paragraph-by-paragraph I usually do...



I use the Fastmail service for e-mail, and have been a user for many
yeras (currently a sort of 'legacy user', since they've changed owners
and systems several times over the years).

FastMail has been on a new site for several years, but have kept a
'classic version' for legacy users; however, in June they'll stop
supporting it, but using SeaMonkey their system says:


Sorry, your browser does not support the technologies needed to use
our web interface. Please make sure you have the latest version, and
that JavaScript is enabled. Learn more about our browser
requirements:


[ ... ]


Are there any other FastMail users on this Forum, or (maybe even if not)
someone may have some idea besides what I described above?

The site to 'open in SM' is:

https://www.fastmail.com/login/


It may be that Fastmail is complaining about SM 2.40 (or more likely,
2.40's User-Agent spoofing of Firefox 43).

In the last month or so before the release of 2.46, I found an
increasing number of sites that were objecting to Seamonkey. I don't use
the Fastmail web interface frequently, but I know that it was
complaining about Seamonkey, in the way that you've described. I have
PrefBar installed, and when I used the tool for browser spoofing, so
that I was showing the current version of Firefox, I had no problems
with FastMail.

I upgraded to the Adrian Kalla contributed build of 2.47 (which has
since upgraded to 2.48), and I can't remember seeing any site complain
about Seamonkey support since then.  And, I've had no problems with
either the 2.47 or 2.48 builds.

Elsewhere in this thread, you mentioned avoiding upgrading out of 2.40
unless there's a compelling reason to do so.  For me, the compelling
reason (and the reason I went to Adrian's contributed build) was the
accumulation of security fixes.  And now that 2.46 is in full release, I
can't see any compelling reason *not* to upgrade to that one, even if
you're not wanting to run a later version on a contributed build.

For your specific case, I really don't think there's anything specific
to Seamonkey's capacities and Fastmail's web UI that aren't also issues
in Firefox 43.0. I won't bother to check spoofing FF 43 against
Fastmail, but I think it very probable that if I were to do so, they
would give me the same error messages that you're reporting.

For Fastmail (and countless other web site operators), what you're
seeing is simply the effects of a world where Web 2.0 is a de facto
standard, and where it's a normal thing that a web site uses JavaScript
(in varying degrees from token to extensive). Although I use NoScript to
block a lot of scripting (and I think a lot of it is egregious), and
it's also possible that part of Fastmail's objection to seeing FF 43.0
may be based on security issues, if you take Fastmail's error message at
face value, they're telling you that in your current setup, your browser
won't render the site in the way that they've designed it.  That could
be merely display quirks, or it could be that there's essential
functionality that won't work, because they've coded it for capacity
that wasn't available in FF 43.0.

At this stage, I think your options are:

- Upgrade to 2.46
- Install PrefBar or User Agent Switcher, and set the User Agent string
to spoof a version of Firefox that Fastmail will accept.

Unless you have specific reasons about 2.46 being unsuitable, I strongly
encourage you to upgrade.


In that part which you substituted by "[ ... ]", I had already said:


No changes to JS (general or in the tab, using PrefBar), SM User
Agents and/or "advertise FF compatibility" helped, but opening the
page in FF worked right away -- so, I think the difference must be
something 'localized'.


I wasn't explicit, but the "changes to SM User Agents" WERE made using 
PrefBar (which I've been using since v.3), and it isn't the case of "a 
version of Firefox that Fastmail will accept", since I have a UA for FF 
43, and it made no difference, while opening an actual FF 41 worked...


Also, as I said in a reply to Daniel:


My problem isn't finding a way to access [the login]:  It's discovering
why my SM 40 on 32-bit XP cannot (exactly because it seems that,
besides a very efficient 'version-sniffing' from FM, there doesn't
seem to be any reason for that, and I'd like to understand why that
happens).


So I CAN login on the new page in FF 41, but cannot do so on SM 2.40!

About the upgrade to 2.46, as I said in a reply to Frank-Rainer Grahl:


I don't have much free time right now (and one of the reasons is
that I'm migrating to a dual-boot XP/W7 system, so discovering, and
learning to handle, the differences about programs on these SOs
(much more work than I expected) takes up much time.

I really would like (including for my own sake) to remember why I
decided to keep on SM 40 for now, but I recall that it's 

Re: Fastmail and SeaMonkey

[NFN Smith]

Alexander Yudenitsch wrote:

I use the Fastmail service for e-mail, and have been a user for many
yeras (currently a sort of 'legacy user', since they've changed owners
and systems several times over the years).

FastMail has been on a new site for several years, but have kept a
'classic version' for legacy users; however, in June they'll stop
supporting it, but using SeaMonkey their system says:


Sorry, your browser does not support the technologies needed to use
our web interface. Please make sure you have the latest version, and
that JavaScript is enabled. Learn more about our browser
requirements:


[ ... ]


Are there any other FastMail users on this Forum, or (maybe even if not)
someone may have some idea besides what I described above?

The site to 'open in SM' is:

https://www.fastmail.com/login/


It may be that Fastmail is complaining about SM 2.40 (or more likely, 
2.40's User-Agent spoofing of Firefox 43).


In the last month or so before the release of 2.46, I found an 
increasing number of sites that were objecting to Seamonkey. I don't use 
the Fastmail web interface frequently, but I know that it was 
complaining about Seamonkey, in the way that you've described. I have 
PrefBar installed, and when I used the tool for browser spoofing, so 
that I was showing the current version of Firefox, I had no problems 
with FastMail.


I upgraded to the Adrian Kalla contributed build of 2.47 (which has 
since upgraded to 2.48), and I can't remember seeing any site complain 
about Seamonkey support since then.  And, I've had no problems with 
either the 2.47 or 2.48 builds.


Elsewhere in this thread, you mentioned avoiding upgrading out of 2.40 
unless there's a compelling reason to do so.  For me, the compelling 
reason (and the reason I went to Adrian's contributed build) was the 
accumulation of security fixes.  And now that 2.46 is in full release, I 
can't see any compelling reason *not* to upgrade to that one, even if 
you're not wanting to run a later version on a contributed build.


For your specific case, I really don't think there's anything specific 
to Seamonkey's capacities and Fastmail's web UI that aren't also issues 
in Firefox 43.0. I won't bother to check spoofing FF 43 against 
Fastmail, but I think it very probable that if I were to do so, they 
would give me the same error messages that you're reporting.


For Fastmail (and countless other web site operators), what you're 
seeing is simply the effects of a world where Web 2.0 is a de facto 
standard, and where it's a normal thing that a web site uses JavaScript 
(in varying degrees from token to extensive). Although I use NoScript to 
block a lot of scripting (and I think a lot of it is egregious), and 
it's also possible that part of Fastmail's objection to seeing FF 43.0 
may be based on security issues, if you take Fastmail's error message at 
face value, they're telling you that in your current setup, your browser 
won't render the site in the way that they've designed it.  That could 
be merely display quirks, or it could be that there's essential 
functionality that won't work, because they've coded it for capacity 
that wasn't available in FF 43.0.


At this stage, I think your options are:

- Upgrade to 2.46
- Install PrefBar or User Agent Switcher, and set the User Agent string 
to spoof a version of Firefox that Fastmail will accept.


Unless you have specific reasons about 2.46 being unsuitable, I strongly 
encourage you to upgrade.


Smith


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

Unable to add a new mail account in SM 2.46 under Windows 10

[Alex Beauroy]

Hi there!!!
I went to Mail & newsgroup account settings via the Edit menu
then to : add account
but the account wizard freezes to the pop up window :"Incoming Server 
Information" suggesting a newsgroup server

I just wanted to add an e-mail account!!!
What should I do
Thanks in advance for your assistance
Best Regards
@lex
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Fastmail and SeaMonkey

[Alexander Yudenitsch]

Hi, Frank-Rainer Grahl! Thanks for writing, on 06 Mar 17 07:23:


maybe it has absolutely nothing to do with the SM version, but
it's something in your system that is different from mine (eg, I'm
using XP on this machine; I'll try it on a W7 one when I get the
chance):  If you were running 2.40, perhaps you would also have no
problems with this site...


You could try with a new test profile. I doubt that running XP makes a
difference unless its about HTML5 content.


As I just said in a reply to Daniel:


since I do get that login page OK on my XP 32-bit FireFox 41, my
problem isn't finding a way to access it:  It's discovering why my
SM 40 on 32-bit XP cannot (exactly because it seems that, besides a
very efficient 'version-sniffing' from FM, there doesn't seem to be
any reason for that, and I'd like to understand why that happens).


So, even if I tried a new profile and it worked, I still wouldn't be 
much closer to discovering the reason for it not working now, and THAT's 
what I'd like.



There were really tons of changes between 2.40 and 2.46 and not only
in the Gecko engine. I ran all versions between 2.40 and 2.46 and
around 2.42 I noticed a considerable speed improvement. But some also
noticed a regression so you just need to try it out yourself.


Unless it's very noticeable, I wouldn't care too much about 'speed' -- 
and, as you said, it seems to vary depending on each specific system 
configuration, so that probably wouldn't motivate me either way.


As I said before, I don't have much free time right now (and one of the 
reasons is that I'm migrating to a dual-boot XP/W7 system, so 
discovering, and learning to handle, the differences about programs on 
these SOs (much more work than I expected) takes up much time.


I really would like (including for my own sake) to remember why I 
decided to keep on SM 40 for now, but I recall that it's something which 
is a 'no turning back':  Sure, a backup can be restored, but once you 
start using the new one for everyday use, going back is very difficult 
and time-consuming -- and recall it was something I might only realize 
wasn't working for me some time onward...  So, since I can upgrade any 
time (I kept SM 39 for quite some time before I felt safe going to 40), 
I decided to wait.



Other than the default search engine bug for which there is a workaround
and the Data Manager hang probably caused by old cruft in
webappsstore.sqlite (just rename or delete it) I am not aware of any
widespread problems with 2.46.


I don't think it was a "widespread problem", but it might be something 
which may not be important to many, but was a problem for some, and it 
seemed it might be so for me, too -- but, unfortunately, I can't recall 
what it was, and don't want to use my time now looking for it, and I'll 
be sure to keep an eye for anything which is relevant to this, and post 
it here if I do find it within a reasonable time period.



I am more concerned now with 2.48+ because there are some reports of
it crashing when using mail and news. Hits some users all the time
and others never. Mostly on Linux.


Something's tugging at my memory on reading that, suggesting the problem 
I mention was a consequence of something done in Gecko/FF, which made a 
change in SM 46, causing that unwanted result (so, it wouldn't be 
changed on any version after 46)...



Absolutely no software is "error free", either, and all SM (and FF)
versions have always been free so that's not relevant too...


Was mean't as a joke :)


So was my reply!  :-))


Seriously probably some new js features did the trick.


Since it isn't clear that the version difference had anything to do
with it, that's just a speculation...


Yes but I had some problems with pages in 2.40 which did go away in
later versions. There were really improvements in HTML5 compatibility
and the JS interpreter.


Noe THAT is somewhat encouraging, and it might be compatible with my not 
getting a login denial on my XP 32-bit FireFox 41, but getting it on my 
XP 32-bit SeaMonkey 40!


--
Thanks beforehand for your attention, and I hope to hear from you soon.

s) Alexander Yudenitsch   



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

Re: Fastmail and SeaMonkey

[Alexander Yudenitsch]

Hi, Daniel! Thanks for writing, on 06 Mar 17 06:35:


https://www.fastmail.com/login/


Clicking that link took me and my SM 2.46 on Win7 WOW directly to a
log-in page.


Thanks for the info, but it still isn't much help:  As I said, I still 
haven't tried it on a Win7 SM (migration should happen RealSoonNow...), 
and I'm not using 2.46 or a 64 system; so, since (as I said before) I do 
get that login page OK on my XP 32-bit FireFox 41, my problem isn't 
finding a way to access it:  It's discovering why my SM 40 on 32-bit XP 
cannot (exactly because it seems that, besides a very efficient 
'version-sniffing' from FM, there doesn't seem to be any reason for 
that, and I'd like to understand why that happens).


--
Thanks beforehand for your attention, and I hope to hear from you soon.

s) Alexander Yudenitsch   



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

Re: Fastmail and SeaMonkey

[Frank-Rainer Grahl]

Alexander Yudenitsch wrote:

Hi, Frank-Rainer Grahl! Thanks for the quick reply:


Meaning that you couldn't do that in 2.40?


Meaning I didn't even try.


So, maybe it has absolutely nothing to do with the SM version, but it's 
something in your system that is different from mine (eg, I'm using XP on this 
machine; I'll try it on a W7 one when I get the chance):  If you were running 
2.40, perhaps you would also have no problems with this site...


You could try with a new test profile. I doubt that running XP makes a 
difference unless its about HTML5 content.


"Unsupported" in this context is meaningless:  What kind of 'support' do we 
have for 2.46?  Besides forums (which should work equally well for 2.40), I 
doubt there's any hope of any one-on-one support for any SM version, now and 
in the foreseeable future:  If the devs manage to keep up with needed new 
versions, we'll all be very thankful (as am I , always).


Every bug report is read even if it stays unconfirmed. If a report is against 
2.40 and can't be easily reproduced in 2.46+ I usually ignore it and/or ask 
for verifying it with a supported version. There were really tons of changes 
between 2.40 and 2.46 and not only in the Gecko engine. I ran all versions 
between 2.40 and 2.46 and around 2.42 I noticed a considerable speed 
improvement. But some also noticed a regression so you just need to try it out 
yourself.


Absolutely no software is "error free", either, and all SM (and FF) versions 
have always been free so that's not relevant too...


Was mean't as a joke :)

You do imply a valid query:  What, exactly, led me to decide to not migrate to 
2.46 now?  While I have seen many advantages (though they hardly sound "miles 
ahead of 2.40", IMHO), there were a few points which led to this decision, but 
I've now 'deleted' them from my 'memory', leaving only the conclusion; since 
that seems worthwhile, I will try to recover exactly which were these points 
(I seem to recall just 2, but enough to counterbalance any not-important-to-me 
advantages), and post it here when I do, but I don't have much free time right 
now, so that may take a while.


Other than the default search engine bug for which there is a workaround and 
the Data Manager hang probably caused by old cruft in webappsstore.sqlite 
(just rename or delete it) I am not aware of any widespread problems with 
2.46. That doesn't mean it will work for you so backup your profile but I ran 
it during the whole beta phase and even gave copies to 2 friends which were 
happy with it. I am more concerned now with 2.48+ because there are some 
reports of it crashing when using mail and news. Hits some users all the time 
and others never. Mostly on Linux.



Seriously probably some new js features did the trick.


Since it isn't clear that  the version difference had anything to do with it, 
that's just a speculation...


Yes but I had some problems with pages in 2.40 which did go away in later 
versions. There were really improvements in HTML5 compatibility and the JS 
interpreter.


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

Re: news.eternal-september.org times out

[Daniel]

On 6/03/2017 5:04 AM, njoracle wrote:

Anyone else having a problem with the connection to news.eternal-september.org
timing out? Started about 20 minutes ago.

Not that it really worried me but, the last two nights at about 
mid-night local (say 13:00 GMT), I've lost access to my 
news.eternal-september.org Usenet account.


Hasn't really worried me, just shut down and went to bed!!

--
Daniel

User agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:49.0) Gecko/20100101 
SeaMonkey/2.46 Build identifier: 20161213183751

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

Re: Fastmail and SeaMonkey

[Daniel]

On 6/03/2017 3:19 AM, Alexander Yudenitsch wrote:

I use the Fastmail service for e-mail, and have been a user for many
yeras (currently a sort of 'legacy user', since they've changed owners
and systems several times over the years).

FastMail has been on a new site for several years, but have kept a
'classic version' for legacy users; however, in June they'll stop
supporting it, but using SeaMonkey their system says:


Sorry, your browser does not support the technologies needed to use
our web interface. Please make sure you have the latest version, and
that JavaScript is enabled. Learn more about our browser
requirements:

To use our web interface, you must have
- Javascript enabled
- Cookies enabled

Cookies - Like all sites, we use these as part of our system for
secure authentication. Our site does not have any ads: the only
cookies set are from us and we do not use cookies for any other
purpose other than authentication. For the best experience

While we make our best effort to support older versions of browsers
wherever possible, we can only support the latest version.
At the least you'll need:
Internet Explorer 8+ (but rich text editing requires IE9+)
Microsoft Edge
Firefox 3.6+
Chrome
Safari 5.1+
Opera 12.17+


No changes to JS (general or in the tab, using PrefBar), SM User Agents
and/or "advertise FF compatibility" helped, but opening the page in FF
worked right away -- so, I think the difference must be something
'localized'.

Are there any other FastMail users on this Forum, or (maybe even if not)
someone may have some idea besides what I described above?

The site to 'open in SM' is:

https://www.fastmail.com/login/

Clicking that link took me and my SM 2.46 on Win7 WOW directly to a 
log-in page.


WFM

--
Daniel

User agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:49.0) Gecko/20100101 
SeaMonkey/2.46 Build identifier: 20161213183751

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