Greasy Fork

still don't work #SOLVED

I have tried it at Firefox 52 ESR/32 (Greasemonkey 3.17), Chromium 60/32 (Tampermonkey 4.4), Win 7/32.
As to other scripts and addons, I once tried it at clean Chromium, with Tampermonkey and Google Search Extra Buttons only.
As to region restriction, I have test it by a global proxy, which can surf well at github, google, youtube etc.
Besides, there are many guys' reports, not only mine.
If possible, will you test it at win7/x86? Mr. spmbt. I know this is a rude request, but I, or rather, we very miss this script, for this script is really excellent.

by the way, yandex extra buttons is working well here

Hi, stint!
Sorry, but in my comps and environments script works normally all time from your last message in June. Fx 52-57 via Greasemonkey on the Win7 or Win10 (4-5 comps), Chrome (actual versions as unpacked extension in developer mode with adding file manifest.json), Vivaldi - all works.

In your case need to debug executing of script in the browser. For example, set console.log(...) in script and checking... Causes for unrunning may be some as written in https://greasyfork.org/ru/forum/discussion/29300/x or https://greasyfork.org/ru/forum/discussion/28230/x (attempt of clean install in second link). May present one of at least 2 causes: another blocking script or absence of found path in DOM in the page for any specifical layout (less of probability).

Hi, stint!
Sorry, but in my comps and environments script works normally all time from your last message in June. Fx 52-57 via Greasemonkey on the Win7 or Win10 (4-5 comps), Chrome (actual versions as unpacked extension in developer mode with adding file manifest.json), Vivaldi - all works.

In your case need to debug executing of script in the browser. For example, set console.log(...) in script and checking... Causes for unrunning may be some as written in https://greasyfork.org/ru/forum/discussion/29300/x or https://greasyfork.org/ru/forum/discussion/28230/x (attempt of clean install in second link). May present one of at least 2 causes: another blocking script or absence of found path in DOM in the page for any specifical layout (less of probability).

thanks for your reply
i will try to do it
wish it will work well again in our computer again

there are some screenshots. not enough? if so, i will try to show more.
i'm not a programmer, almost knowing nothing about javascript or any other machine laguage, so very probably i don't get your idea very well.
thanks for your patience and effort.
at last, i report my browser again, Firefox [b]52.4.0 ESR[/b]


DOM log:
https://greasyfork.org/zh-CN/forum/uploads/FileUpload/6b/5b1446726510defe2c58c61ed8bc2a.zip

Yes, you are show cause of problem ("This operation is insecure") when JS executes localStorage() access. But I have not this message in console. Googling shows: https://www.google.ru/search?num=20&newwindow=1&source=hp&ei=AC32WbG8Mqub6ASCg4SADw&q=firefox+localStorage+error+this+operation+is+unsecure

Number of error messages speak about situation when localStorage has incorrect access with disabling of cookie. It would not be associated by rules of JS. May be, it is a bug of Firefox. (It may to understand as disabling of cookie disables access to localStorage also. But in correct browser this operation is absent.)

I not use any access to cookie in my script, but this effect may be present (?) if you disable cookie in preferences or by another extension such as Noscript. I was not disable cookie in my browser and not test this case and not know behavior of browser. (Many sites will not work, I think.)

You may try to enable cookie and test, but if it is cause of this error, it is not correct behavior of browser (bug). Also, attempt, please to install script in Chrome browser, it would be work on it.

(Thanks for zip, but it not contain useful info and will not need in future.)

thanks for your long reply
those days occupied I was, and return now.
there is no no script at firefox, only ublock origin, but I do change the default setting about cookie, don't accept the third-party ones.
as your advice, I will try it at chrome again, and then report the progress.

Finally, I get it back, at chrome 62.0.3202.89.
Besides, it also work well at firefox 38 ESR.
If someone else encounters similar problem, maybe you just need to change the version of the browser.
thanks.

News about this theme:
I found such settings in the about:config page:

extensions.webextensions.default-content-security-policy
and
extensions.webextensions.base-content-security-policy

My (default browser's) value of the first key, for example, is "script-src 'self'; object-src 'self';" and of second key is "script-src 'self' https://* moz-extension: blob: filesystem: 'unsafe-eval' 'unsafe-inline'; object-src 'self' https://* moz-extension: blob: filesystem:;".

If you have more text in its, this text may influence to security policy. Attemt to change (right mouse button - Reset) these fields and read info about this problem and feature in JS specifiation:https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Content-Security-Policy/script-src . These CSP may set by any site and there are default settings which may be changed by some program (include malware) or manually.

News about this theme:
I found such settings in the about:config page:

extensions.webextensions.default-content-security-policy
and
extensions.webextensions.base-content-security-policy

My (default browser's) value of the first key, for example, is "script-src 'self'; object-src 'self';" and of second key is "script-src 'self' https://* moz-extension: blob: filesystem: 'unsafe-eval' 'unsafe-inline'; object-src 'self' https://* moz-extension: blob: filesystem:;".

If you have more text in its, this text may influence to security policy. Attemt to change (right mouse button - Reset) these fields and read info about this problem and feature in JS specifiation:https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Content-Security-Policy/script-src . These CSP may set by any site and there are default settings which may be changed by some program (include malware) or manually.

thanks