Open j4k0xb opened 3 weeks ago
Turning off Brave Shields or any other adblocker can bring it back to normal, it should be a problem caused by site scripts conflicting with TM and adblocker.
That's unfortunate... This site is infested with ads Gonna look what filter in https://github.com/uBlockOrigin/uAssets causes it
You can also try to set Content Script API
to UserScripts API Dynamic
. By doing so the script might run earlier than uBO's injected filter snippets.
That's unfortunate... This site is infested with ads Gonna look in what filter in https://github.com/uBlockOrigin/uAssets causes it
@j4k0xb It could be a script conflict, not related to filtering rules. And the console didn't get any useful information.
You can also try to set
Content Script API
toUserScripts API Dynamic
. By doing so the script might run earlier than uBO's injected filter snippets.
@derjanb The UserScripts API Dynamic
mode doesn't help.
BTW. TM 5.3.6209 BETA does not resolve issue #2164, Whenever the browser is updated, GM_info.userAgentData
returns still the original version number in UserScripts API Dynamic
mode.
The same script works in Violentmonkey btw, so I think it's a Tampermonkey issue
The same script works in Violentmonkey btw, so I think it's a Tampermonkey issue
Violentmonkey also has problems. You can try running the following script. The window.atob method will report an error. @j4k0xb @tophf
// ==UserScript==
// @name New script
// @namespace Violentmonkey Scripts
// @match https://streamtape.com/*
// @grant unsafeWindow
// @version 1.0
// @author -
// @description test
// @run-at document-start
// ==/UserScript==
console.group("unsafeWindow")
console.log(unsafeWindow.atob);
console.log(unsafeWindow.atob("QQ=="))
console.groupEnd("unsafeWindow")
console.group("window")
console.log(window.atob);
console.log(window.atob("QQ=="))
console.groupEnd("window")
The window.atob method will report an error.
nope it works fine
The window.atob method will report an error.
nope it works fine
with uBlock Origin?
voilentmonkey with uBO:
document_start
probably depends on which extension was installed first. If uBO runs first it mangles atob
somehow. I'd say it's a bug in uBO filters, because breaking such basic functions is overly destructive.document_start
requires you to enable "Synchronous page mode" option.
- The order in which extensions run at
document_start
probably depends on which extension was installed first. If uBO runs first it manglesatob
somehow. I'd say it's a bug in uBO filters, because breaking such basic functions is overly destructive.- Since Violentmonkey is still MV2, a real
document_start
requires you to enable "Synchronous page mode" option.
Hi @tophf , I already enabled "Synchronous page mode" option, but it did not work.
And I fixed it by GM_addElement to get window.atob
, and thanks for your reply.
Expected Behavior
Execute the userscript.
Actual Behavior
Script isn't executed. This only happens for this site on brave (works on firefox). Same behavior with Tampermonkey beta.
page logs:
background.js logs:
Specifications
Script