Fix 'prevent-setTimeout' — scriptlet does not work on vikingf1le.us.to

[ghajini]

when i use vikingf1le.us.to#%#//scriptlet('prevent-setTimeout', 'location.href') ,this does not work as per STR below google chrome 135.0.7049.85 , AdGuard Browser extension Version 4.4.49

STR=

• add

vikingf1le.us.to#%#//scriptlet('prevent-addEventListener', 'DOMContentLoaded', 'history.go')
vikingf1le.us.to#%#//scriptlet('prevent-setTimeout', 'location.href')

• navigate to https://vikingf1le.us.to/f/iySXxBllSm
• wait for page load
• In that same tab navigate to https://vikingf1le.us.to/f/iySXxBllSk
• ad redirection occurs to https://gxh1yqz2v.xyz/?data-user=iLkjlqK10IcQ1g4tyLjaS6IP3BP2& due to script below

<script>
      setTimeout(function() {
         window.location.href = atob('aHR0cHM6Ly9neGgxeXF6MnYueHl6Lz9kYXRhLXVzZXI9aUxramxxSzEwSWNRMWc0dHlMamFTNklQM0JQMiY=');
      }, 2000);

   </script>

[AdamWr]

That's rather extension issue related to https://github.com/AdguardTeam/AdguardBrowserExtension/issues/2855 and scriptlet is executed too late. I cannot reproduce it with app for Windows. It also does not occur with extension with devtools opened and cache disabled.

[ghajini]

so https://github.com/AdguardTeam/AdguardBrowserExtension/issues/2855#issuecomment-2709094050

fix bug here?

[kodiakhub]

so AdguardTeam/AdguardBrowserExtension#2855 (comment)

fix bug here?

Yes, the latest version is "mv2 v5.1.70". However, it's still not fully fixed, because it continues to cause the "late injection" issue when the "Filtering Log" window is open. This isn't a problem for end users, but it might be an issue for advanced users and filter maintainers/volunteers.