The JSON output can be often large, and the logger might not be optimal when trying to analyze these. I was trying to figure how I could make this easier but then I realized there is already a way to make this easier:

• Select "info" in filter expression picker
• Open export tool (the clipboard icon)
• Toggle to "List" mode
• Toggle to "Plain" mode

Now you can freely go through all output, select, copy/paste, etc.

the logger might not be optimal when trying to analyze these but then I realized there is already a way to make this easier:

The console is still way better, I can't wrap my head around reading and analyzing these logs in the logger.
I might consider using an older uBO version just for having logs in the console.

I think leaving from console is good, as we no more need to care about anti-devtools at least for this. It's just the current logger is not ideal.

How about making the logger to have two tabs, the one is the old logger and the other is for these?

Thanks for spotting this, a typo indeed. This prevented from turning off verbose mode in the logger.

In fx & latest dev

You mean you compared latest Firefox dev build with stable Firefox built?

Ok I see a difference between Firefox stable and dev build. I will investigate when I can.

i used firefox stable only
& filters

1cloudfile.com##+js(no-fetch-if, /adsbygoogle\.js|\.js/ method:HEAD)
1cloudfile.com##+js(no-fetch-if)
1cloudfile.com##+js(nosiif, !display)

1. ubo stable 1.55 =
   https://github.com/uBlockOrigin/uBlock-issues/assets/20338483/b4177578-f6a1-4d05-a5aa-353bd3df9830

2. ubo dev 1.55.1b24=

https://github.com/uBlockOrigin/uBlock-issues/assets/20338483/0d637619-6a3e-48a6-9c75-beb2e2548fc7

expected is i should see Please Disable adblock ... when only 1cloudfile.com##+js(no-fetch-if) is used but recent ubo dev is breaking

recent ubo dev is breaking

We shouldn't say "breaking" just because the behavior is different. The site appears to be trapping calls to console.log, and since the new dev build doesn't use console.log for the involved scriptlets, it's possible this is what is causing the different behavior.

the message about antiadb is hidden when used logging scriptlet no-fetch-if , i think can be fixed

gorhill/uBlock@1db54c4

Hmmm, japscan.lol##+js(nowoif, , , log) doesn't log on 1.55 too, nevetheless the rule works.

Do not use log anymore in any scriptlet, this was useful only when outputing to console. Now if logger is opened, it will output whatever there is to output. If japscan.lol##+js(nowoif) doesn't work, then I need to fix it -- I just need feedback about what trace information you want to see in logger. So I will add arguments information for nowoif. Also, if verbose mode in enabled, it will also output not-prevented calls to window.open.

Okay, japscan.lol##+js(nowoif) logs this

I want to know what window.open arguments, in particular url, it prevented. But the situation is the same for 1.55.0 or AG, maybe some problem on Chrome or the site.

II modified the scriptlet to return more information -- in next dev build.

From now on I won't be able to do anything today and in the coming days, so hopefully the next devbuild will be good enough.

Yes, in version 1.55.1b27 in Google Chrome 109 the problem (aeld) is solved.

example.com##+js(aost, property)
https://github.com/uBlockOrigin/uBlock-discussions/discussions/841#discussioncomment-7777610

Thanks. Confirm it works.