Only now it is difficult to get out of this situation as they find a wiki with information or understand how JS code works without reading discussions and wikis.

Another reason is that I wanted to be sure that if stray filters with log/debug find their way into the lists, they won't cause issues with dev tools. This might have been the main reason.

Yes, website authors skilled with development tools will just install uBO dev build, and in the end nothing we can think of is going to stop them.

Will log functionality be available for dev build only? I thought it was just at the moment and will come to stable too.

Yes, website authors skilled with development tools will just install uBO dev build, and in the end nothing we can think of is going to stop them.

How about also requirng filterAuthorMode true? Sure they can find, but better than nothing?

What's a really convincing argument for having this available in stable build?

No, I meant adding another barrier in dev build. But maybe site owner who found using dev build will too find the flag...

worth of creating proper issue here https://github.com/uBlockOrigin/uBlock-issues/issues

• i noticed when i go here eg https://www.youtube.com/shorts/GxUDZK9dQaA , i see broken ui with youtube.com##+js(aeld)
  

• without filter
  

Not uBO specific, same issue with AdGuard.

If I remove the logging of the element id on which the listener was added, the issue goes away. It seems Youtube may be trapping the access to the id property of an element and this causes failure somewhere.

So the logging of the element details was added as per request: uBlockOrigin/uBlock-issues#3061 (comment).

Accessing the id is causing an issue on Youtube, presumably because somewhere in Youtube's huge pile of JS, there is a trap which act on accessing the id of an element. I tried various things and somehow replacing:

    if (  elem.id !== '' ) { parts.push(`#${CSS.escape(elem.id)}`); }

With:

    const id = String(elem.id);
    if ( id !== '' ) { parts.push(`#${CSS.escape(id)}`); }

Ends up solving the issue -- kind of a voodoo-esque solution...

gorhill/uBlock@8eb3b19

I don't know. If eventually nobody uses it, probably.

gorhill/uBlock@1d9ee00

I think set-constant and acis don't support the new way of passing optional parameters (They don't have get-extra-args.fn as dependency).

joysound.com##+js(set, document.body.oncopy, null, 3)
=>
joysound.com##+js(set, document.body.oncopy, null, runAt, 3)

I will work on this in next dev cycle.