Different from pref to disallow javascript, period...
Many pages need js enabled in order to display/render properly...
...but many ALSO contain pain-in-the-ass scripted behaviors ~~ xhttp requests to refresh chatbox, refresh "status updates" etc.
In a separate request (one which I labeled "need badly") I requested a "Stop" navigation button.
That, as an interface element, could fit the bill here ~~ regardless whether or not the page is loading, or has finished loading... clicking stop button would suspend/kill further script operations within the visible tab.
I do realize that, upon clicking stop, some "stuffs" on a page will appear broken (e.g. a jquery-powered menu, etc). That's fine ~~ if necessary, I'll refresh the page. In the meantime, while trying to READ the page... the distracting slidey-show and chatbox and such are thwarted. Pong. Are you still connected? (nyah, nyah, not so far as YOU know)
Ah, overlapping with this request... I should request ability (pref) to disallow SPDY (until/unless we can intercept/inspect the content)
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Different from pref to disallow javascript, period...
Many pages need js enabled in order to display/render properly...
...but many ALSO contain pain-in-the-ass scripted behaviors ~~ xhttp requests to refresh chatbox, refresh "status updates" etc.
In a separate request (one which I labeled "need badly") I requested a "Stop" navigation button.
That, as an interface element, could fit the bill here ~~ regardless whether or not the page is loading, or has finished loading... clicking stop button would suspend/kill further script operations within the visible tab.
I do realize that, upon clicking stop, some "stuffs" on a page will appear broken (e.g. a jquery-powered menu, etc). That's fine ~~ if necessary, I'll refresh the page. In the meantime, while trying to READ the page... the distracting slidey-show and chatbox and such are thwarted. Pong. Are you still connected? (nyah, nyah, not so far as YOU know)
Ah, overlapping with this request... I should request ability (pref) to disallow SPDY (until/unless we can intercept/inspect the content)
Button for stopping JavaScript running after they have been loaded?
Hmmm... that could be tricky. It depends of the QtWebKit.
I won't say it's impossible but very tricky if the QtWebKit rendering engine itself does not support it.
Have to check.