Re: STRANGE problem reaching https://manpages.debian.org/

[Mason83]

On 10/05/2018 15:43, Richard Owlett wrote:

> I'm running Debian 9 installed via netinst in February with some 
> packages added via Synaptic and run neither Update nor Upgrade explicitly.
> 
> My browser is SeaMonkey 2.49.1 downloaded from 
> https://www.seamonkey-project.org/ . I have no 
> add-ins/add-ons/extensions/etc installed.
> 
> I routinely browse with JavaScript disabled.
> 
> I've not had any problems with https://manpages.debian.org/ in the past.
> This morning I'd visited a site which required JavaScript.
> Without having disabled JavaScript I attempted to visit 
> https://manpages.debian.org/ .
> It never loaded. There were NO error messages.
> After disabling JavaScript there was no problem reaching the site.
> I repeated the enable/disable JavaScript sequence several times.
> The problem is repeatable.
> 
> I posted to the debian-user list 
> [https://lists.debian.org/debian-user/2018/05/msg00339.html].
> 
> I got a response stating:
>> Hm, worked fine here, although I only have ff (59.0.2) with ublock
>> (although it's stating nothing was blocked).
>>
>> The page does load some javascript though -- looks to do something with
>> the fonts / css, but it's been a while since I've used JS ...
> 
> I responded:
>>
>> I've the "Firefox ESR" that was installed by default.
>> It loaded  https://manpages.debian.org/ OK.
>> I don't know if it has JavaScript enabled nor do I know how to check.
>> Don't know how to verify its version either.
>> Tried ff a few time in past. Never liked it. 
> 
> Comments/suggestions?

I have NoScript, but debian.org is whitelisted.

https://manpages.debian.org/  loads correctly for me (2.49.2 in Zindoze)

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

Re: Why does "STOP" Button not appear ?

[NFN Smith]

WaltS48 wrote:

On 5/10/18 11:35 AM, NFN Smith wrote:

David E. Ross wrote:

It seems that the Stop button does not work on long-running scripts,
including malformed JavaScript.  When I encounter this, I use PrefBar to
disable JavaScript.



A similar approach would be in using NoScript to block all scripts as 
a default, and then granting access to individual scripting only as 
needed.





Anyway, when Fox News looks like it is taking forever to load, I just 
Reload the tab.


A good first step.  Clearing the cache can also be useful.  That's a 
nice thing that PrefBar makes easily available.


Smith

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

Re: Why does "STOP" Button not appear ?

[WaltS48]

On 5/10/18 11:35 AM, NFN Smith wrote:

David E. Ross wrote:

It seems that the Stop button does not work on long-running scripts,
including malformed JavaScript.  When I encounter this, I use PrefBar to
disable JavaScript.



A similar approach would be in using NoScript to block all scripts as a 
default, and then granting access to individual scripting only as needed.


On a lot of sites (especially media ones), there's a lot of scripting 
going on.  Some of it is necessary for getting to the content that you 
want, but there's quite a bit of scripting that's used to deliver 
graphics, animation, advertising and other eye-candy, as well as quite a 
bit that's essentially usage tracking.


In my own usage, I tend to leave scripts from places like Google 
Analytics, Google Tag Manager, Facebook, Amazon, etc. blocked unless I'm 
having problems getting a page to display correctly. Conversely, 
scripting hosts that have "CDN" in the name tend to be "content delivery 
network", and often mirrors of the content you want.  On the other hand, 
I've learned to identify a number of scripting hosts that are ad 
delivery networks, and have found that it's generally safe to 
permanently blacklist.


The one challenge for selectively enabling scripting hosts is that for 
some, there's a cascading effect. Sometimes, the script (and scripting 
host) that is needed for the content you want is actually delivered 
through another scripting host. Thus, if you go to site A, and enable 
their scripting, you may also have to enable scripts from site B, and in 
turn, site C, before you get the content you want.  But if you're 
blocking several other scripts, it may be worth it, of having less 
tracking, less animation, and less hung scripts.


Smith


Sorry, for the fast fingered empty followup.

Anyway, when Fox News looks like it is taking forever to load, I just 
Reload the tab.


--
GO GOLDEN KNIGHTS!
National Popular Vote 
Ubuntu 16.04LTS - Unity Desktop
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Why does "STOP" Button not appear ?

[NFN Smith]

David E. Ross wrote:

It seems that the Stop button does not work on long-running scripts,
including malformed JavaScript.  When I encounter this, I use PrefBar to
disable JavaScript.



A similar approach would be in using NoScript to block all scripts as a 
default, and then granting access to individual scripting only as needed.


On a lot of sites (especially media ones), there's a lot of scripting 
going on.  Some of it is necessary for getting to the content that you 
want, but there's quite a bit of scripting that's used to deliver 
graphics, animation, advertising and other eye-candy, as well as quite a 
bit that's essentially usage tracking.


In my own usage, I tend to leave scripts from places like Google 
Analytics, Google Tag Manager, Facebook, Amazon, etc. blocked unless I'm 
having problems getting a page to display correctly. Conversely, 
scripting hosts that have "CDN" in the name tend to be "content delivery 
network", and often mirrors of the content you want.  On the other hand, 
I've learned to identify a number of scripting hosts that are ad 
delivery networks, and have found that it's generally safe to 
permanently blacklist.


The one challenge for selectively enabling scripting hosts is that for 
some, there's a cascading effect. Sometimes, the script (and scripting 
host) that is needed for the content you want is actually delivered 
through another scripting host. Thus, if you go to site A, and enable 
their scripting, you may also have to enable scripts from site B, and in 
turn, site C, before you get the content you want.  But if you're 
blocking several other scripts, it may be worth it, of having less 
tracking, less animation, and less hung scripts.


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

Re: Why does "STOP" Button not appear ?

[WaltS48]

On 5/10/18 11:35 AM, NFN Smith wrote:

David E. Ross wrote:

It seems that the Stop button does not work on long-running scripts,
including malformed JavaScript.  When I encounter this, I use PrefBar to
disable JavaScript.



A similar approach would be in using NoScript to block all scripts as a 
default, and then granting access to individual scripting only as needed.


On a lot of sites (especially media ones), there's a lot of scripting 
going on.  Some of it is necessary for getting to the content that you 
want, but there's quite a bit of scripting that's used to deliver 
graphics, animation, advertising and other eye-candy, as well as quite a 
bit that's essentially usage tracking.


In my own usage, I tend to leave scripts from places like Google 
Analytics, Google Tag Manager, Facebook, Amazon, etc. blocked unless I'm 
having problems getting a page to display correctly. Conversely, 
scripting hosts that have "CDN" in the name tend to be "content delivery 
network", and often mirrors of the content you want.  On the other hand, 
I've learned to identify a number of scripting hosts that are ad 
delivery networks, and have found that it's generally safe to 
permanently blacklist.


The one challenge for selectively enabling scripting hosts is that for 
some, there's a cascading effect. Sometimes, the script (and scripting 
host) that is needed for the content you want is actually delivered 
through another scripting host. Thus, if you go to site A, and enable 
their scripting, you may also have to enable scripts from site B, and in 
turn, site C, before you get the content you want.  But if you're 
blocking several other scripts, it may be worth it, of having less 
tracking, less animation, and less hung scripts.


Smith



--
GO GOLDEN KNIGHTS!
National Popular Vote 
Ubuntu 16.04LTS - Unity Desktop
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Why does "STOP" Button not appear ?

[David E. Ross]

On 5/9/2018 9:15 PM, DoctorBill wrote:
> I remember back with previous versions of SeaMonkey, that there was a "STOP"
> button that stopped a page that was loading - if you clicked it.
> 
> MANY web sites (like FoxNews) come up with the STOP Button greyed out (not
> functional).
> 
> Why is that ?
> 
> Some web sites take FOREVER to load and I would like to STOP the 
> loading.can't !
> 
> DoctorBill
> 

It seems that the Stop button does not work on long-running scripts,
including malformed JavaScript.  When I encounter this, I use PrefBar to
disable JavaScript.

-- 
David E. Ross


First you say you do, and then you don't.
And then you say you will, but then won't.
You're undecided now, so what're you goin' to do?
From a 1950s song
That should be Donald Trump's theme song.  He obviously
does not understand "commitment", whether it is about
policy or marriage.
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

STRANGE problem reaching https://manpages.debian.org/

[Richard Owlett]

I'm running Debian 9 installed via netinst in February with some 
packages added via Synaptic and run neither Update nor Upgrade explicitly.


My browser is SeaMonkey 2.49.1 downloaded from 
https://www.seamonkey-project.org/ . I have no 
add-ins/add-ons/extensions/etc installed.


I routinely browse with JavaScript disabled.

I've not had any problems with https://manpages.debian.org/ in the past.
This morning I'd visited a site which required JavaScript.
Without having disabled JavaScript I attempted to visit 
https://manpages.debian.org/ .

It never loaded. There were NO error messages.
After disabling JavaScript there was no problem reaching the site.
I repeated the enable/disable JavaScript sequence several times.
The problem is repeatable.

I posted to the debian-user list 
[https://lists.debian.org/debian-user/2018/05/msg00339.html].


I got a response stating:

Hm, worked fine here, although I only have ff (59.0.2) with ublock
(although it's stating nothing was blocked).

The page does load some javascript though -- looks to do something with
the fonts / css, but it's been a while since I've used JS ...


I responded:


I've the "Firefox ESR" that was installed by default.
It loaded  https://manpages.debian.org/ OK.
I don't know if it has JavaScript enabled nor do I know how to check.
Don't know how to verify its version either.
Tried ff a few time in past. Never liked it. 


Comments/suggestions?
TIA

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

Re: Why does "STOP" Button not appear ?

[WaltS48]

On 5/10/18 12:15 AM, DoctorBill wrote:
I remember back with previous versions of SeaMonkey, that there was a 
"STOP"

button that stopped a page that was loading - if you clicked it.

MANY web sites (like FoxNews) come up with the STOP Button greyed out (not
functional).

Why is that ?

Some web sites take FOREVER to load and I would like to STOP the 
loading.can't !


DoctorBill



Works here. SeaMonkey 2.49.3

Does the "STOP" button work on FoxNews if you run SeaMonkey in safe mode?

--
GO GOLDEN KNIGHTS!
National Popular Vote 
Ubuntu 16.04LTS - Unity Desktop
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Why does "STOP" Button not appear ?

[Daniel]

DoctorBill wrote on 10/05/18 14:15:
I remember back with previous versions of SeaMonkey, that there was a 
"STOP"

button that stopped a page that was loading - if you clicked it.

MANY web sites (like FoxNews) come up with the STOP Button greyed out (not
functional).

Why is that ?

Some web sites take FOREVER to load and I would like to STOP the 
loading.can't !


DoctorBill


Doctor Bill, it's my understanding that the "Stop" button will only be 
active whilst you are actually downloading data for that web site. Once 
you have all the info, the button would grey out.


I don't know why the button would be greyed out if a web site is slow in 
getting downloaded.


Is the button becoming active at all??

--
Daniel

User agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 
SeaMonkey/2.49.1 Build identifier: 20171016030418


User agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 
SeaMonkey/2.49.1 Build identifier: 20171015235623

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

Re: Why does "STOP" Button not appear ?

[GerardJan]

DoctorBill wrote:

DoctorBill wrote:

I remember back with previous versions of SeaMonkey, that there was a "STOP"
button that stopped a page that was loading - if you clicked it.


use /CANCEL/

MANY web sites (like FoxNews) come up with the STOP Button greyed out (not
functional).

Why is that ?

Some web sites take FOREVER to load and I would like to STOP the 
loading.can't !


DoctorBill


Using 2.49.1 right now.



--
https://facebook.com/gerardjan.vinkesteijn

User agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Firefox/52.0 
SeaMonkey/2.49.3

Build identifier: 20180403170715

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