Re: HTML5 support

[David C. Mores via support-seamonkey]

Ken Rudolph wrote:
Running SeaMonkey 2.49.1 on updated Win10, with modified user agent: 
Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Firefox/59.0.3


Netflix sent me a link in SeaMonkey e-mail to watch a short message from 
the Crown.  However when I click on the link [shown below] it doesn't 
play in the SeaMonkey browser, rather I get a message about Netflix 
system requirements for HTML5 Player and Silverlight.  No add-ons from 
Mozilla that I try seem to work to rectify this problem.


When I use Firefox, Chrome or Edge browsers, and use the same link it 
plays fine on all 3.  But the point of SeaMonkey is that a link in 
e-mail goes to the SM browser.  Maybe if there were an easy way to set 
links in SM e-mail to go to one of the other browsers that would be 
useful...but not optimal, of course.


Anyway, the e-mail link in question:

https://www.netflix.com/watch/80230267?trkid=13710079&MSG_TITLE=80230267&lnktrk=EMP&g=F78B0997B0E061CD360DCEAFCB6432116452765C&lkid=CROWN_S2_MESSAGE_WATCH 



How can I get SM to play this link?

--
Ken Rudolph



I'm a Netflix subscriber and I normally remain logged in on the Netflix 
site.  When I clicked on the link, I got a page for "The Crown" but no 
arrow to start the video.  However, at the top of the page there was a 
banner with "Netflix" on left and "Sign Out" on the right.  After 
signing out, I got a page with an arrow link to start the video which 
did in fact play it.


User agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 
Firefox/52.0 SeaMonkey/2.49.1

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

Re: Diverge From T-bird

[David C. Mores via support-seamonkey]

Ed Mullen wrote:

On 6/10/17 at 8:39 PM, David C. Mores's prodigious digits fired off with
great aplomb:

EE wrote:

rickman wrote:

When using SeaMonkey for reading newsgroups, I see a number of
differences from T-bird.  One that is particularly annoying is when
reading a thread new posts often show up in the middle with other parts
of the thread outside of the thread pane.  An easy way to see if any
other posts remain unread in this thread is to use the \ key to close
the thread.  If an underline remains I could then press 'N' to take me
to the next unread post in that thread in T-bird.  In SeaMonkey it
takes
me to the first unread post in the GROUP!

Obviously this is a divergence from T-bird.  Was this something that
was
changed in SeaMonkey or in T-bird?

I find any number of differences in usability like this.  I think if I
could get T-bird to work on my machine I would switch back.  But it ran
even slower than SeaMonkey does, so SeaMonkey is a net improvement,
just
not a large one.

For that matter, why did SeaMonkey split off from T-bird?  What was the
fundamental issue that created a new tool so similar to the old?


What do you mean, "outside of the thread pane"? If a thread exists, it
has to be in the thread pane, unless you think that some part of it was
not sent.

SeaMonkey did not split from Thunderbird.  Thunderbird and Firefox split
off from the Mozilla suite, and SeaMonkey was a continuation of the
Mozilla suite, only kept more up to date by having the cores of
Thunderbird and Firefox.


As I recall it from the discussion at the time, Thunderbird and
Firefox were created as separate, single function applications to make
them faster and more responsive than the combined multi-function
application.


That was part of the rationale.



I never understood or appreciated this view because I always found the
Seamonkey multi-function application to be entirely responsive and
fast enough for me.  Like what are we talking about?  300ms verses
500ms or some such - not really perceptible for most of us in day to
day usage. Having the mail and browser app, etc. rolled into one
seemed to be - and continues to be - a supremely convenient and
efficient way to go, but your mileage and situation may vary.


A long time ago, because of the faster/lighter argument, I did a
comparison of SM vs separate apps.



The original was done, I think, in 2006. I re-ran them in 2013.



Thanks for adding your quantitative study information to this 
discussion.  It's interesting, and made me realize that my comments on 
fastness were about operational fastness and not about the app startup 
time fastness - which likely is what the original FF/TB/SM discussion 
was about.

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

Re: Diverge From T-bird

[David C. Mores via support-seamonkey]

EE wrote:

rickman wrote:

When using SeaMonkey for reading newsgroups, I see a number of
differences from T-bird.  One that is particularly annoying is when
reading a thread new posts often show up in the middle with other parts
of the thread outside of the thread pane.  An easy way to see if any
other posts remain unread in this thread is to use the \ key to close
the thread.  If an underline remains I could then press 'N' to take me
to the next unread post in that thread in T-bird.  In SeaMonkey it takes
me to the first unread post in the GROUP!

Obviously this is a divergence from T-bird.  Was this something that was
changed in SeaMonkey or in T-bird?

I find any number of differences in usability like this.  I think if I
could get T-bird to work on my machine I would switch back.  But it ran
even slower than SeaMonkey does, so SeaMonkey is a net improvement, just
not a large one.

For that matter, why did SeaMonkey split off from T-bird?  What was the
fundamental issue that created a new tool so similar to the old?


What do you mean, "outside of the thread pane"? If a thread exists, it
has to be in the thread pane, unless you think that some part of it was
not sent.

SeaMonkey did not split from Thunderbird.  Thunderbird and Firefox split
off from the Mozilla suite, and SeaMonkey was a continuation of the
Mozilla suite, only kept more up to date by having the cores of
Thunderbird and Firefox.

As I recall it from the discussion at the time, Thunderbird and Firefox 
were created as separate, single function applications to make them 
faster and more responsive than the combined multi-function application.


I never understood or appreciated this view because I always found the 
Seamonkey multi-function application to be entirely responsive and fast 
enough for me.  Like what are we talking about?  300ms verses 500ms or 
some such - not really perceptible for most of us in day to day usage. 
Having the mail and browser app, etc. rolled into one seemed to be - and 
continues to be - a supremely convenient and efficient way to go, but 
your mileage and situation may vary.

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

Re: Basic Authentication issue in 2.46

[David C. Mores via support-seamonkey]

Gerry Hickman wrote:

I have a SiteCom router with an embedded web server. For many years I
was able to log in from SeaMonkey by typing http://10.0.0.1/ and then
the user name and password. This still works in older versions of SM and
FF, but not in SM 2.46

I believe the issue is related to a new HTTP header being sent by SM 2.46

Upgrade-Insecure-Requests: 1

I set up a raw HTTP test on a linux VM (without using a browser) and
tested both with and without this header.

Request with header : Authentication FAILS
Request without header : Authentication WORKS

It's quite strange, as I don't see how the router can even know about
this header as it's too old. I also noticed something even more odd, if
I change the header to something like

BlahBlahBalh: 1

the authentication also fails, but if I use

BlahBlahBalh: one

everything starts working

Is it possible to disable the 'Upgrade-Insecure-Requests' header in
SeaMonkey?



I found this same behavior with my Linksys/Cisco WRT120N home router 
that I bought in 2010.  Since SeaMonkey is based pretty much on Firefox 
code, I checked it there with the same result.  So I decided to file a 
bug report on Firefox because any fix there would/should migrate to the 
SeaMonkey code.


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

The Comment story started 4 months ago and has recently concluded that 
my router is the bad boy.  It has been at end-of-life status according 
to Linksys/Cisco for about 6 years.  The only workaround I have is, as 
you have found, to use the older version of SM, or another browser such 
as Google Chrome, MS Edge or Pale Moon - that apparently do not (yet) 
send the Upgrade-Insecure-Header in the request.


This header mechanism is legitimate W3C:
https://w3c.github.io/webappsec-upgrade-insecure-requests/
I looks like we got to learn to live with it.

How old is your SiteCom router?  Have you looked into available firmware 
upgrades for it?

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

Re: Browser not authentication-capable or authentication failed.

[David C. Mores]

Edmund Wong wrote:

David C. Mores wrote:

I am trying to login on my Cisco/Linksys WRT120N home router admin page
at http://192.168.0.1/ using seamonkey.  I get a pop up window prompting
for 'A username and password are being requested by http://192.168.0.1.
The site says: "WRT120N"'  Clicking the OK button after entering the
info causes the window to close, but pop up again.  Clicking the Cancel
button results in an error page:

401 Authorization Required
Browser not authentication-capable or authentication failed.

I think this may be a bug in seamonkey V2.46 Build identifier:
20161213183751 because the very same login using the Google Chrome or MS
Edge browsers work just fine - i.e. a successful router login.



I'm not entirely sure why the build identifier would make any
difference; and since you've tried the safe mode, can you try it
with 2.40?  What about Firefox?

Edmund

Yes it does work for SM 2.40, and no it does not work in the latest FF 
50.  What do you recommend now?


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

Re: Browser not authentication-capable or authentication failed.

[David C. Mores]

Lee wrote:

On 1/7/17, David E. Ross  wrote:

On 1/7/2017 9:27 AM, David C. Mores wrote:

I am trying to login on my Cisco/Linksys WRT120N home router admin page
at http://192.168.0.1/ using seamonkey.  I get a pop up window prompting
for 'A username and password are being requested by http://192.168.0.1.
The site says: "WRT120N"'  Clicking the OK button after entering the
info causes the window to close, but pop up again.  Clicking the Cancel
button results in an error page:

401 Authorization Required
Browser not authentication-capable or authentication failed.

I think this may be a bug in seamonkey V2.46 Build identifier:
20161213183751 because the very same login using the Google Chrome or MS
Edge browsers work just fine - i.e. a successful router login.

I can find no setting in about:config that seem to control
authentication capabilities.

My workaround is to use the other browsers, but I normally use seamonkey
for everything.

Have you seen this?  Ideas?  Bug report it?

Thanks,
Dave



This might be bug #435013.  See
<https://bugzilla.mozilla.org/show_bug.cgi?id=435013>.  Currently, there
is no work-around; and I do not see any indication that a fix is being
developed.


Probably not since it's clear-text instead of https:

A username and password are being requested by http://192.168.0.1


I'd check javascript is enabled & cookies are allowed, then try
disabling addons or starting seamonkey in safe mode.

Lee



No joy on Lee's suggestions.  Identical symptoms.

David Ross's pointer to bug 435013, I think, does not apply, as Lee 
pointed out.  Not a cert issue.


I'll wait to see if other suggestions come in before filing a bug report.

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

Browser not authentication-capable or authentication failed.

[David C. Mores]

I am trying to login on my Cisco/Linksys WRT120N home router admin page 
at http://192.168.0.1/ using seamonkey.  I get a pop up window prompting 
for 'A username and password are being requested by http://192.168.0.1. 
The site says: "WRT120N"'  Clicking the OK button after entering the 
info causes the window to close, but pop up again.  Clicking the Cancel 
button results in an error page:


401 Authorization Required
Browser not authentication-capable or authentication failed.

I think this may be a bug in seamonkey V2.46 Build identifier: 
20161213183751 because the very same login using the Google Chrome or MS 
Edge browsers work just fine - i.e. a successful router login.


I can find no setting in about:config that seem to control 
authentication capabilities.


My workaround is to use the other browsers, but I normally use seamonkey 
for everything.


Have you seen this?  Ideas?  Bug report it?

Thanks,
Dave

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

Re: Why are functions being broken and not fixed ?

[David C. Mores]

Rubens wrote:

Hello all,


Since one year ago I have been observing some Seamonkey features/functions
to stop working and no fixes being provided to them, as follows:

1- Empty message pane opens by itself after marking a message as junk in
the messages list
(Bug # 986874, opened on March 22, 2014 and still unresolved)

2- After clicking on the "Show remote content" button from a received
e-mail message,
and adding its sender to the "allowed" list, the yellow alert stripe
pops-up again
like as nothing had been done.

3- When selecting a newsgroup message to be opened in a new tab, it
appears as a blank page.

The reason for writing this is that in every release I always see new
functions being added,
but I think it would be nice to fix previously working (and now broken)
functions also.



Rubens


I will second this observation, especially #2.
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Lightning in SeaMonkey 2.33

[David C. Mores]

Thee Chicago Wolf (MVP) wrote:

On Thu, 19 Mar 2015 17:56:00 -0400, Rob Steinmetz
 wrote:


I just upgraded to 2.33 and Lightning is broke, at least on my computer.
I upgraded to Lightning 3.8b2 and nothing works. I tried the
calendar.icaljs fix posed elsewhere but it was already set to false.

Any ideas I don't seem to be alone but it is apparently somewhat random.


You need Lightning 3.9b.

Same problem here.  However, 3.9b is for SM 2.34 and is incompatible 
with 2.33.  SM 2.34 is not available for download yet.

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

Re: about:config

[David C. Mores]

Philip TAYLOR wrote:


David C. Mores wrote:


On the about:config page what is the difference between line items that are 
bolded or not bolded?

User set ?

You are probably right.  I did not make the association of the Status 
column entries.  However, there must be more to it than just that.  Why 
are they bolded when their seems to be just two Status types - "default" 
and "user set"?

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

Yahoo RSS feed link URL corrupted in SM 2.15

[David C. Mores]

I view the RSS feed "Today" (ID 1468442) on My Yahoo page, and since SM 
2.15, I am seeing the link URL's on this feed being corrupted so that 
when I click on one, I get a "Sorry, the page you requested was not 
found" message.  After much testing and comparing, it seems that the 
link displayed when I do a 'mouse over' on a feed item is like this: 
http://my.yahoo.com/wanna-eat-why-crazy-cute-181909139.html , but should 
be http://news.yahoo.com/wanna-eat-why-crazy-cute-181909139.html . 
Every 'mouse over' on the Today feed shows 'my.yahoo.com' where it 
should be '.yahoo.com'.


Yahoo is not doing this because on other systems where I can run an 
older version of SM (2.14), this does not happen.


Does anyone else see this?

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

Re: about:config

[David C. Mores]

David E. Ross wrote:

On 1/19/13 8:11 AM, David C. Mores wrote:

On the about:config page what is the difference between line items that
are bolded or not bolded?

Thanks,
Dave



Bold items have values that are not the default values.  You have done
something to change the values of those preference variables.  You might
have done that explicitly by going to [Edit > Preferences] on the menu
bar, via about:config, or editing the user.js file in your profile.  You
might have changed a value implicitly by the way you browse or the pages
you visited.



That makes comprehensive sense.  Thanks!
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

about:config

[David C. Mores]

On the about:config page what is the difference between line items that 
are bolded or not bolded?


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

Did Seamonkey Window behavior change?

[David C. Mores]

In recent versions of Seamonkey I started seeing a change in behavior 
for new Seamonkey windows in a Win7 environment.  When clicking on a 
link in a Seamonkey Mail message, a new or existing Seamonkey browser 
window opens/pops on the top of the desktop.  Then, but not always, a 
second or so later, that window falls to the bottom with the previous 
Seamonkey top window returning to the top with no action on my part.  I 
am not certain how to reproduce this reliably.


This does not seem normal to me.  Are others seeing this behavior?  If 
it is new, purposeful behavior, what is the purpose?  Is there an option 
to shut if off?

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

Re: Seamonkey 2.x default printer printing broken

[David C. Mores]

Robert Kaiser wrote:

David C. Mores wrote:

I ran Firefox 3.0 under Linux to see how it behaves with printing.


Don't compare with outdated Firefox versions like 3.0, compare with at
least 3.5 which uses the same code as SeaMonkey 2.0 does.

Robert Kaiser


Okay - I just tried Firefox 3.6 and the print behavior is the same as 3.0.
And after trying a printer different from the default, the next print
operation does not remember the last printer used, but reverts to the
original default.

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

Re: Seamonkey 2.x default printer printing broken

[David C. Mores]

Robert Kaiser wrote:

david c mores wrote:

David E. Ross wrote:

As I recall, SeaMonkey 1.x always defaulted to the last printer you
requested. SeaMonkey 2.x is doing the same thing.


I am incline to agree with you on this. However, the current 2.0.3
version of Seamonkey on Linux
definitely does not remember the printer used during the same session on
the second or later print operation.


We're using the default GNOME print dialogs on Linux (and Windows system
ones on Windows).

Anything that sucks in those dialogs, sucks in the system (in GNOME if
you're on Linux - and yes, there's a few things there).

Robert Kaiser


I ran Firefox 3.0 under Linux to see how it behaves with printing.  The print 
function used
for the first time does highlight the printer defined by my LPDEST or PRINTER
environment variable.  There is no 'user_pref("print.print_printer", h213a);' 
entry in the prefs.js
or user.js file.  So it would seem that either Firefox does not use GNOME
print dialogs or if it is, then Seamonkey is not following GNOME print dialogs
as closely as Firefox.  Anyway, there is a disconnect here.

I think the desired behavior for Seamonkey should be to provide a reasonable 
convenient
behavior for print defaults like Firefox.

Please advise,
Dave
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Seamonkey 2.x default printer printing broken

[david c mores]

David E. Ross wrote:

On 23-Feb-10 12:28 PM, david c mores wrote:

In our enterprise environment we have hundreds of printers to choose from.  
Printing from Seamonkey 2.0 does not
seem to work the way it did under 1.x.

I have set the environment variables LPDEST and PRINTER to the name of my 
default printer queue.

This is RHEL5 that uses CUPS.

When I click on the Print button in Seamonkey 2, the Print window comes up and 
the highlighted printer is
the first on in the sorted list.  I would expect the window to be positioned 
and highlighted on my default
printer. Instead I have to scroll done the list to find my printer and press 
the Print button to complete
my print request.

So it would seem that Seamonkey 2 is not honoring default printers.  The help 
docs do not help on this.

Please advise,
Dave


As I recall, SeaMonkey 1.x always defaulted to the last printer you
requested.  SeaMonkey 2.x is doing the same thing.


I am incline to agree with you on this.  However, the current 2.0.3 version of 
Seamonkey on Linux
definitely does not remember the printer used during the same session on the 
second or later print operation.



The workaround for this is as follows:

1.  Go to the folder containing your profile.  (Hint:  It should contain
files named prefs.js, bookmarks.html, and cookies.sqlite.)

2.  Using a text editor, open (or create) the file user.js.

3.  Insert the following entry into user.js:
user_pref("print.print_printer", xxx);
where xxx is the name of your desired default printer.  If the name
contains blanks, it must be enclosed within quotes.  Note that the
semi-colon at the end is required.  (I always insert a comment after an
entry to explain why the entry is there; comments begin with //.)

4.  Save the edited user.js.

This will restore your desired default printer every time you terminate
and then restart SeaMonkey.  It will NOT work if SeaMonkey is running
continuously in the background on a computer that is not rebooted.  It
will work only if SeaMonkey is completely terminated and then launched
de novo.  The preference variables entered in user.js overwrite the
corresponding preference variables in prefs.js only during the launching
of SeaMonkey.

For example, I have the following in my user.js:
user_pref("print.print_printer", "HP Color LaserJet CP1215");
// default back to actual printer if another printer was
// selected (e.g., Acrobat Distiller)



Thanks for your detailed reply, but this definitely does not work under Linux 
Seamonkey.
The print window always positions to the first printer available on the system.
The print.print_printer user_pref can be in the prefs.js or the user.js.
It makes no different.  Both are ignored. I know I have the right files in
my .mozilla/seamonkey/ directory because the file time stamps are current.

Sounds like you are running on Windows?

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

Seamonkey 2.x default printer printing broken

[david c mores]

In our enterprise environment we have hundreds of printers to choose from.  
Printing from Seamonkey 2.0 does not
seem to work the way it did under 1.x.

I have set the environment variables LPDEST and PRINTER to the name of my 
default printer queue.

This is RHEL5 that uses CUPS.

When I click on the Print button in Seamonkey 2, the Print window comes up and 
the highlighted printer is
the first on in the sorted list.  I would expect the window to be positioned 
and highlighted on my default
printer. Instead I have to scroll done the list to find my printer and press 
the Print button to complete
my print request.

So it would seem that Seamonkey 2 is not honoring default printers.  The help 
docs do not help on this.

Please advise,
Dave
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey