You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I performed a cursory search of the issue tracker to avoid opening a duplicate issue
Your issue may already be reported.
I tried to reproduce the issue when...
uBlock Origin is the only extension
uBlock Origin with default lists/settings
using a new, unmodified browser profile
I am running the latest version of uBlock Origin
I checked the documentation to understand that the issue I report is not a normal behavior
Description
This is a suggestion to change script:inject logging to the new +js name, because it's shorter and thus allows the inject parameters to be more visible. Plus uAssets recently converted to the new name.
I've been logging with +js in my fork since March. The only extra item needed is a small reverse-lookup converter, like this.
I also suggest changing the logged type to script instead of dom. It has the advantage of better text filtering, e.g. using script| to see all script activity or !|dom to hide all cosmetics while still seeing injects.
(I also changed the ^script:has-text log type to inline-script for the same reasons.)
The text was updated successfully, but these errors were encountered:
Prerequisites
Description
This is a suggestion to change script:inject logging to the new
+js
name, because it's shorter and thus allows the inject parameters to be more visible. Plus uAssets recently converted to the new name.I've been logging with +js in my fork since March. The only extra item needed is a small reverse-lookup converter, like this.
I also suggest changing the logged type to
script
instead ofdom
. It has the advantage of better text filtering, e.g. usingscript|
to see all script activity or!|dom
to hide all cosmetics while still seeing injects.(I also changed the ^script:has-text log type to
inline-script
for the same reasons.)The text was updated successfully, but these errors were encountered: