Page 1 of 1

Button does not work

Posted: 2018-06-28, 22:41
by cartel

Re: Button does not work

Posted: 2018-06-28, 23:51
by therube
Works here.
Did you try Safe Mode?

Re: Button does not work

Posted: 2018-06-29, 05:29
by Moonchild
Are you using NoScript? 8-)

Re: Button does not work

Posted: 2018-06-29, 21:24
by cartel
I allowed everything with noscript and then allowed scripts globally and the button didn't work.
I had to disable/remove noscript to get it to work.

Looks like its time to find a noscript alternative.
2017013.jpg

Re: Button does not work

Posted: 2018-06-30, 10:49
by therube
You need to try again.
There is no issue with NoScript & that site.

+googletagservices.com
+www.googleapis.com
+google.com
+searchtempest.com

Direct, gives you areas in CA.
BC, Alberta, Skeena...

Single, gives you listings.
OEM AM/FM/Cassette, Honda Civic OEM Factory Original, Honda Civic Coup 2003...

Re: Button does not work

Posted: 2018-06-30, 12:05
by cartel
therube wrote:You need to try again.
There is no issue with NoScript & that site.

+googletagservices.com
+www.googleapis.com
+google.com
+searchtempest.com

Direct, gives you areas in CA.
BC, Alberta, Skeena...

Single, gives you listings.
OEM AM/FM/Cassette, Honda Civic OEM Factory Original, Honda Civic Coup 2003...
This is what I get with that button.

Timestamp: 6/30/2018 5:04:52 AM
Error: TypeError: googletag.pubads(...).setTargeting is not a function
Source File: https://static.searchtempest.com/www/js ... 4b15bdf.js
Line: 237

Re: Button does not work

Posted: 2018-06-30, 12:22
by Moonchild
cartel wrote:I allowed everything with noscript and then allowed scripts globally and the button didn't work.
I had to disable/remove noscript to get it to work.
This is exactly the kind of behavior we warn NoScript users for and why we don't provide official support for people using that extension. Even if it *should* work, it still often doesn't.

Re: Button does not work

Posted: 2018-06-30, 12:30
by therube
That's from Error Console.
I'm not coming across that.

As a test, create a new, clean Profile.
Only install NoScript.
Verify that the site works.

Re: Button does not work

Posted: 2018-06-30, 12:50
by therube
If you don't want to provide support, that's fine.
If a user chooses to use an extension that blocks content, well that is on them.
If a user can't get a site to work with an extension that they've chosen to use, that too is their issue.

But, in this case, the usage of NoScript is not an issue in PM on that site.
Clicking the button does work as expected.
Granted, you do need to figure out what domains you need to allow, but that comes with the territory.
That site does not work particularly well as it is.
The site works MUCH better, with NoScript installed, blocking all kinds of crap that would otherwise materially (at least on my end) affect browser operations.
My browser experience on that site is much better with NoScript installed.


(And all that said, depending just what you do, how you do with NoScript, on that site I did see some oddities, attributable, I believe to refreshing of the ads on the site, where the NoScript icon went into "spasms". Or did it? Or was it the status bar load indicator that was spasm-ing? Might have been the latter?)

Re: Button does not work

Posted: 2018-06-30, 22:29
by cartel
OK I fixed it.
You have to remove noscript, restart, then search about:config for noscript, remove all entries except capability.policy.maonoscript.sites.
Copy the data from that line to a text file, then reset the string. (reset = delete for those that dont know)
Then restart PM and install noscript 5.1.8.4. Import your text file to the whitelist (this is a good time to remove all http sites from that list).
Done.
You cant simply update the browser and expect noscript to work, you must follow these steps.

I hope this helps.


OK that did work till you restart PM and then it wont work.
Try that rube, restart PM and see if the button works after that.
I've wasted enough time, noscript is being ridiculous.

Re: Button does not work

Posted: 2018-07-01, 00:18
by cartel
Well I'm trying umatrix but it seems useless. Also its abandoned for firefox legacy and only supports webextentions.

When I block google .ca with noscript, I get what I want, tools where I can see them and not hidden, wasting my time like google seems to like being a difficult asshat.
2017020.jpg
Umatrix doesn't seem to want to block the script, instead blocks the whole page, which make it worthless to me.
2017021.jpg
2017022.jpg
So unless Therube has a solution to make noscript work post restart of PM, I'm pretty much screwed.

Re: Button does not work

Posted: 2018-07-01, 00:39
by cartel
OK so its this ABE "thing" thats doing it.
https://noscript.net/abe/

ABE off the button works as expected.
ABE was co-operating for years but since Basilisk and PM 28 it refuses.

Re: Button does not work

Posted: 2018-07-01, 01:16
by ron_1
Off-topic:
cartel wrote:
Looks like its time to find a noscript alternative.
uBlock Origin, in advanced user mode, can block scripts. And without the annoyances that NoScript can cause (at least for me, so far).

Re: Button does not work

Posted: 2018-07-01, 03:22
by cartel
helloimustbegoing wrote:
Off-topic:
cartel wrote:
Looks like its time to find a noscript alternative.
uBlock Origin, in advanced user mode, can block scripts. And without the annoyances that NoScript can cause (at least for me, so far).
Off-topic:
Here is an example of google blocked with NS vs allowed.
If you can tell me how to do this in 1 click on Ublock/matrix I'd be all for it.
Notice the comfortable layout with stable buttons and better use of whitespace?
Thats what google and almost everyone for that matter want to remove for some stupid reason.
Make everything difficult, time consuming and misleading to boot.
Also note the search results, total garbage.
2017023.jpg
2017024.jpg
So this is most defiantly a problem of ignorance on my part of the ABE function in noscript and not an issue with PM.
The reason why it chose to work/notwork in version 27 to 28 remains a mystery.

Re: Button does not work

Posted: 2018-07-01, 10:30
by yami_
You can get the older Google interface by changing your Google user agent override to something like this:

Code: Select all

Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:3.4) Goanna/20180610 PaleMoon/27.9.3