A Windows XP help forum. PCbanter

If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below.

Go Back   Home » PCbanter forum » Microsoft Windows XP » General XP issues or comments
Site Map Home Register Authors List Search Today's Posts Mark Forums Read Web Partners

halting browsers loading pages



 
 
Thread Tools Display Modes
  #1  
Old October 20th 17, 12:34 PM posted to microsoft.public.windowsxp.general
J. P. Gilliver (John)[_4_]
external usenet poster
 
Posts: 2,679
Default halting browsers loading pages

When I open a browser, I have them set to load the tabs I had last time;
I find this useful. However, this means they load fully one of those
tabs (probably the one I had focus on when I closed the browser
previously). (I have them set _not_ to load _all_ the pages represented
by the tabs, just the one with focus; if I want to look at one of the
other tabs, I click on it, and it then loads.)

However, I sometimes just load a browser to quickly check something on a
new webpage. When I do this, if the page (tab) that has focus is a
complex one, I just click on the "stop loading" button (the "X" turns
into the "reload" icon), so that I can have the browser's full attention
for the new tab I'm about to open.

But: although I've told it to stop loading the page, and the "X" (stop
loading) has changed to the "reload" symbol, often the page keeps doing
something - there is a circling symbol in the tab for Chrome, and
whatever progress indication I have in Firefox-plus-addons still shows
something. (I notice it more in Chrome, but I think it happens in
Firefox too.)

Why do pages keep "doing something" after I've clicked to tell them to
stop? And can anything be done about it, short of changing the browser
setting to not load the tabs from last time, which I don't want to do?
--
J. P. Gilliver. UMRA: 1960/1985 MB++G()AL-IS-Ch++(p)Ar@T+H+Sh0!:`)DNAf

"Grammar is there to help, not hinder."
-- Mark Wallace, APIHNA, 2nd December 2000 (quoted by John Flynn 2000-12-6)
Ads
  #2  
Old October 20th 17, 04:01 PM posted to microsoft.public.windowsxp.general
JJ[_11_]
external usenet poster
 
Posts: 744
Default halting browsers loading pages

On Fri, 20 Oct 2017 12:34:45 +0100, J. P. Gilliver (John) wrote:

Why do pages keep "doing something" after I've clicked to tell them to
stop? And can anything be done about it, short of changing the browser
setting to not load the tabs from last time, which I don't want to do?


Then web browser's Stop button is only effective for foreground network
requests which are triggered by HTML codes. e.g. HTML files served in a
frame, JS files, CSS files, image files, and font files.

Background network request are triggered directly by JavaScript code, and
they're not stoppable via the Stop button. This doesn't include network
requests which are triggered from a JavaScript injected HTML elements. e.g.
an image shown on a popup message. The only way to stop background network
requests is by closing the tab. This is because the network request instance
is kept by the JavaScript code. Disabling the JavaScript feature of the
browser also won't stop them either, because what affected is only the
JavaScript functionality, not the network requests (which already been
issued). However, it possible to stop background network requests using
GreaseMonkey script.
  #3  
Old October 20th 17, 07:50 PM posted to microsoft.public.windowsxp.general
J. P. Gilliver (John)[_4_]
external usenet poster
 
Posts: 2,679
Default halting browsers loading pages

In message , JJ
writes:
[]
Then web browser's Stop button is only effective for foreground network
requests which are triggered by HTML codes. e.g. HTML files served in a
frame, JS files, CSS files, image files, and font files.

Background network request are triggered directly by JavaScript code, and
they're not stoppable via the Stop button. This doesn't include network
requests which are triggered from a JavaScript injected HTML elements. e.g.
an image shown on a popup message. The only way to stop background network
requests is by closing the tab. This is because the network request instance


I feared as much )-:.

is kept by the JavaScript code. Disabling the JavaScript feature of the
browser also won't stop them either, because what affected is only the
JavaScript functionality, not the network requests (which already been
issued). However, it possible to stop background network requests using
GreaseMonkey script.


Ah: not heard of that. Is it complicated?
--
J. P. Gilliver. UMRA: 1960/1985 MB++G()AL-IS-Ch++(p)Ar@T+H+Sh0!:`)DNAf

This was before we knew that a laboratory rat, if experimented upon, will
develop cancer. [Quoted by] Anne ), 1997-1-29
  #4  
Old October 20th 17, 08:21 PM posted to microsoft.public.windowsxp.general
Paul[_32_]
external usenet poster
 
Posts: 11,873
Default halting browsers loading pages

J. P. Gilliver (John) wrote:
In message , JJ
writes:

However, it possible to stop background network requests using
GreaseMonkey script.


Ah: not heard of that. Is it complicated?


There are several plugins available, for adding userscripts
to web page presentations.

Say I set the trigger to "microsoft.com". And microsoft
has some sort of privacy stealing code on all their web
pages. I can craft a page of .js, which modifies the
browser behavior, but only while microsoft.com web pages
are being fetched.

It allows you to add features on a per-website or domain basis.

I got my first userscript running a couple days ago,
under TamperMonkey, in MSEdge (Win10). No, I don't know how
to write Javascript, so this is a joke of course :-) This
is a great tool for web developers, while they're surfing
the web, if they want to fix/modify stuff. For people who
don't know Javascript, there is a site full of thousands
of scripts to download... but the level of trust is the
same as downloading EXEs from random web sites.

It's no more complicated than... writing your own browser in C.

Paul
  #5  
Old October 20th 17, 08:47 PM posted to microsoft.public.windowsxp.general
VanguardLH[_2_]
external usenet poster
 
Posts: 10,881
Default halting browsers loading pages

J. P. Gilliver (John) wrote:

When I open a browser, I have them set to load the tabs I had last
time; I find this useful. However, this means they load fully one of
those tabs (probably the one I had focus on when I closed the browser
previously). (I have them set _not_ to load _all_ the pages
represented by the tabs, just the one with focus; if I want to look
at one of the other tabs, I click on it, and it then loads.)

However, I sometimes just load a browser to quickly check something
on a new webpage. When I do this, if the page (tab) that has focus is
a complex one, I just click on the "stop loading" button (the "X"
turns into the "reload" icon), so that I can have the browser's full
attention for the new tab I'm about to open.


Create another shortcut to the web browser that opens the about:blank
page. You gave no mention of which web browser you are using but the
command line syntax is similar for specifying a URL. For example:

"path\webbrowserEXE" about:blank

The path and filename to the web browser's executable might contain
spaces and why I show that string enclosed in double quotes. Spaces are
not allowed in URLs (except by escaping them using the % character and
their hex code) so you don't need to double-quote the URL string.

Most times when I load the web browser, I am going somewhere specific.
If I click on a hyperlink, that string gets passed to the web browser.
But if I am going to enter the URL myself into the address bar of the
web browser, I do not want it to load any other pages, just the one that
I intend to enter. Unlike you, I rarely load a web browser and want it
loading pages that I won't be visiting during that web session. So I
set the home page in the web browser to about:blank (or have it open its
"New tab" page and have an extension change it from that noisy set of
tiles that end up connecting to those sites to just a blank tab - which
is not the same as loading about:blank).

Since you want to mostly want to reload pages from a prior web session
in a new web session, you'll need to shortcut that process by using a
different command line to load the web browser. Some web browsers will
open in safe mode by holding down the shift key when you click on their
desktop or Start menu shortcut which should not open any old tabs from a
prior web session. This Shift key trick works with Firefox. Doesn't
work in Google Chrome. However, safe mode also means none of your
extensions will get loaded in that web session (they're disabled). If
you want your extensions available in the new web session then you need
to tell Firefox what URL to open in the command you use to load Firefox.

But: although I've told it to stop loading the page, and the "X"
(stop loading) has changed to the "reload" symbol, often the page
keeps doing something - there is a circling symbol in the tab for
Chrome, and whatever progress indication I have in
Firefox-plus-addons still shows something. (I notice it more in
Chrome, but I think it happens in Firefox too.)

Why do pages keep "doing something" after I've clicked to tell them
to stop? And can anything be done about it, short of changing the
browser setting to not load the tabs from last time, which I don't
want to do?


JJ already answered that. Doesn't see the "why" is important to you.
You want to load the web browser without loading any old web pages
previously visited that were in open tabs on a prior exit of the web
browser.

Your choices a
- Configure the web browser to NOT reload old tabs from the just-prior
web session. Instead learn to save all the tabs in a bookmark folder
(right-click on a tab and save all as a bookmark folder).
That's what I do when I want to return to the same sites in a later
web session. I usually name the bookmark folder "resume" or a topic
that reflects what all the pages are about.
- Create a separate shortcut that tells the web browser to load the
about:blank internal page.
- With Firefox, hold down the Shift key when clicking on its shortcut to
load in its safe mode (all extensions will be disabled).

There might be other workarounds but those are the ones I can think of
right now.
  #6  
Old October 20th 17, 09:46 PM posted to microsoft.public.windowsxp.general
J. P. Gilliver (John)[_4_]
external usenet poster
 
Posts: 2,679
Default halting browsers loading pages

In message , VanguardLH
writes:
J. P. Gilliver (John) wrote:

[Why doesn't clicking "stop loading" actually stop loading?]
Create another shortcut to the web browser that opens the about:blank
page. You gave no mention of which web browser you are using but the


(Sorry, thought I did: Firefox 26, and Chrome last-that-works-in-XP.)

command line syntax is similar for specifying a URL. For example:

"path\webbrowserEXE" about:blank

The path and filename to the web browser's executable might contain
spaces and why I show that string enclosed in double quotes. Spaces are
not allowed in URLs (except by escaping them using the % character and
their hex code) so you don't need to double-quote the URL string.


Good bit of lateral thinking there! I wouldn't have thought of that. But
it wouldn't work for when I open the browser by clicking on a link in an
email or news post, though.

Most times when I load the web browser, I am going somewhere specific.
If I click on a hyperlink, that string gets passed to the web browser.
But if I am going to enter the URL myself into the address bar of the
web browser, I do not want it to load any other pages, just the one that
I intend to enter. Unlike you, I rarely load a web browser and want it
loading pages that I won't be visiting during that web session. So I


That's where we differ. I tend to leave the browser open, with various
tabs that I use a lot open. (If asked _why_, I'd say because of the time
it [either of them] takes to open - which the number of tabs doesn't
seem to affect much, since I have it set to only actually _load_ one.)
[]
Since you want to mostly want to reload pages from a prior web session
in a new web session, you'll need to shortcut that process by using a
different command line to load the web browser. Some web browsers will
open in safe mode by holding down the shift key when you click on their
desktop or Start menu shortcut which should not open any old tabs from a
prior web session. This Shift key trick works with Firefox. Doesn't
work in Google Chrome. However, safe mode also means none of your
extensions will get loaded in that web session (they're disabled). If
you want your extensions available in the new web session then you need
to tell Firefox what URL to open in the command you use to load Firefox.


I can never be sure, though, that if I start a don't-load-old-tabs
session, when I close that session, it won't save the new set of tabs -
or single tab - and thus lose the set of tabs I had previously. (Plus,
see above about opening by clicking on a link.)

But: although I've told it to stop loading the page, and the "X"
(stop loading) has changed to the "reload" symbol, often the page
keeps doing something - there is a circling symbol in the tab for
Chrome, and whatever progress indication I have in
Firefox-plus-addons still shows something. (I notice it more in
Chrome, but I think it happens in Firefox too.)

Why do pages keep "doing something" after I've clicked to tell them
to stop? And can anything be done about it, short of changing the
browser setting to not load the tabs from last time, which I don't
want to do?


JJ already answered that. Doesn't see the "why" is important to you.


True. The main reason I asked the "why" is that I just like to know such
things, and JJ's answer answered that, as far as I can understand. I
still don't understand why the _browser_'s indication - the circling
circle in Chrome - still continues after I've used the _browser_'s stop
button. Surely if the browser knows I've hit stop, it should either
stop, or think it has stopped even if something else is still going on.

You want to load the web browser without loading any old web pages
previously visited that were in open tabs on a prior exit of the web
browser.

Your choices a
- Configure the web browser to NOT reload old tabs from the just-prior
web session. Instead learn to save all the tabs in a bookmark folder
(right-click on a tab and save all as a bookmark folder).
That's what I do when I want to return to the same sites in a later
web session. I usually name the bookmark folder "resume" or a topic
that reflects what all the pages are about.


I do that from time to time (I name it with the date of the save); I
just find it tedious to have to do that every time I close the browser.

- Create a separate shortcut that tells the web browser to load the
about:blank internal page.


That's a good one, which I may think about. Not too good for opening the
browser by clicking on a link, but could still be useful.

- With Firefox, hold down the Shift key when clicking on its shortcut to
load in its safe mode (all extensions will be disabled).


That one I'm not too sure about as I'd always be afeared it would lose
my saved tabs (by overwriting with its own, probably tiny, set) when it
closes.

There might be other workarounds but those are the ones I can think of
right now.


I do appreciate your input, thanks.
--
J. P. Gilliver. UMRA: 1960/1985 MB++G()AL-IS-Ch++(p)Ar@T+H+Sh0!:`)DNAf

Capital flows toward lower costs like a river to lowest ground.
"MJ", 2015-12-05
  #7  
Old October 21st 17, 03:41 AM posted to microsoft.public.windowsxp.general
JJ[_11_]
external usenet poster
 
Posts: 744
Default halting browsers loading pages

On Fri, 20 Oct 2017 19:50:57 +0100, J. P. Gilliver (John) wrote:
In message , JJ
writes:
is kept by the JavaScript code. Disabling the JavaScript feature of the
browser also won't stop them either, because what affected is only the
JavaScript functionality, not the network requests (which already been
issued). However, it possible to stop background network requests using
GreaseMonkey script.


Ah: not heard of that. Is it complicated?


Pretty much, if you're not familiar with programming. It's a software
development.
  #8  
Old October 21st 17, 04:42 AM posted to microsoft.public.windowsxp.general
J. P. Gilliver (John)[_4_]
external usenet poster
 
Posts: 2,679
Default halting browsers loading pages

In message , JJ
writes:
On Fri, 20 Oct 2017 19:50:57 +0100, J. P. Gilliver (John) wrote:
In message , JJ
writes:
is kept by the JavaScript code. Disabling the JavaScript feature of the
browser also won't stop them either, because what affected is only the
JavaScript functionality, not the network requests (which already been
issued). However, it possible to stop background network requests using
GreaseMonkey script.


Ah: not heard of that. Is it complicated?


Pretty much, if you're not familiar with programming. It's a software
development.


Thanks.
--
J. P. Gilliver. UMRA: 1960/1985 MB++G()AL-IS-Ch++(p)Ar@T+H+Sh0!:`)DNAf

science is not intended to be foolproof. Science is about crawling toward the
truth over time. - Scott Adams, 2015-2-2
 




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is Off
HTML code is Off






All times are GMT +1. The time now is 11:37 PM.


Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2024, Jelsoft Enterprises Ltd.
Copyright ©2004-2024 PCbanter.
The comments are property of their posters.