aeld with log argument - formerly aell

[Procyon-b]

I can't seem to make it work.
I'm even trying the examples provided in the wiki, but still nothing is displayed.

wikipedia.org##+js(aeld, { "type": "/.^/", "log": 2 })

"Above filter will log all calls without defusing any of them (because type can't match anything)"

I've tested with FF 112.0.2 + uBO 1.49.0 and with chrome 109 + uBO 1.49.2
I also still have an old chrome 7x with uBO 1.46.0 where I've tested with wikipedia.org##+js(aell)

aell gives me a full listing of all eventlisteners (there are 79), while aeld shows nothing in FF and chrome.

I've checked in the logger that the filter is really applied.

What am I doing wrong?

[mapx-]

your filter is working fine on my end

[krystian3w]

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.

[gorhill]

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.

[Yuki2718]

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

[gorhill]

Stays dev build only.

[Yuki2718]

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?

[gorhill]

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

[Yuki2718]

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

[gorhill]

Well it turns out a new way to pass extra parameters is working rather well I think, like with the new sed scriptlet, where pairs of extra parameters can be passed (position-independent), so I think this should be the way to go instead of the JSON approach. This would make using logging less cumbersome:

wikipedia.org##+js(aeld, /.^/, , runAt, idle, log, 1)

[ghajini]

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
  

[gorhill]

Not uBO specific, same issue with AdGuard.

[gorhill]

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.

[gorhill]

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

[garry-ut99]

peace2000 : #17907 (reply in thread) @ gorhill How can I nowadays log every event on a page by using aeld? The current, documented filter: example.com##+js(aeld, _, , log, 3) Doesn't log anything anymore.

I've discovered a more up-to-date (02.2024) aeld log related subdiscussion in another, semi-related discussion : uBlockOrigin/uBlock-issues#3096 (comment) which says that _ and log have become obsolete ways of logging scriptlets and that _ doesn't work anymore (though log still does sometimes) and that the current way is ##+(aeld) which prints all logs, but doesn't defuse anything (will print "called" only).

peace2000 : Probably wiki should be updated but I'm not comfortable to do so because I'm not fully sure how to scriptlet is intended to work

Yes, "first" and "second" log examples from WiKi don't work anymore due to being deprecated, and the "third" one which still works, has been made redundant by the current one (##+js(aeld)), and seems to work only by accident: as empty/incorrect/surplus parameters are being ignored/skipped, what results in behavior equivalent to ##+js(aeld), in all following examples (still more examples can be crafted):

wikipedia.org##+js(aeld, , , )
wikipedia.org##+js(aeld, , , , , )
wikipedia.org##+js(aeld, , , x, y, z)
wikipedia.org##+js(aeld, , , x, y, z, log, 3)
wikipedia.org##+js(aeld, , , a, b, c, log, 9)
wikipedia.org##+js(aeld, _, , log, 3)
wikipedia.org##+js(aeld, , , log, 3)

[MasterKia]

so I think this should be the way to go instead of the JSON approach

Will the JSON approach be deprecated?

[gorhill]

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

[MasterKia]

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)

[gorhill]

I will work on this in next dev cycle.