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
Basically, in the continuity of the json-prune scriptlet (and the $jsonprune modifier, allowing more advanced queries currently), it can be pretty neat and logical to have a trusted-json-set scriptlet (and a $jsonset modifier), I would say. To either define new or modify existing JSON properties, instead of pruning them.
Some websites / web apps (TF1, M6 too nowadays, etc.) require certain (ad-related) JSON properties to be both present and boolean.
↪️ Currently fixed using JS rules but hey … let's improve/simplify that! 😉
Thank you very much! 👍
P.S. In a discussion I had a while ago with @ameshkov, there was talk of a possible untrusted version limited to true/false/etc. (i.e. a basic json-set scriptlet, thus following the same pattern as set-constant and trusted-set-constant), but probably still too risky though, I would say.
Hello,
Basically, in the continuity of the
json-prune
scriptlet (and the$jsonprune
modifier, allowing more advanced queries currently), it can be pretty neat and logical to have atrusted-json-set
scriptlet (and a$jsonset
modifier), I would say. To either define new or modify existing JSON properties, instead of pruning them.Some websites / web apps (TF1, M6 too nowadays, etc.) require certain (ad-related) JSON properties to be both present and boolean.
↪️ Currently fixed using JS rules but hey … let's improve/simplify that! 😉
Thank you very much! 👍
P.S. In a discussion I had a while ago with @ameshkov, there was talk of a possible untrusted version limited to true/false/etc. (i.e. a basic
json-set
scriptlet, thus following the same pattern asset-constant
andtrusted-set-constant
), but probably still too risky though, I would say.Related discussions:
The text was updated successfully, but these errors were encountered: