JSONPath: Bracketed filter valid in JSONPath tool but not in filter

[Stevoisiak]

Prerequisites

• I verified that this is not a filter list issue. Report any issues with filter lists or broken website functionality in the uAssets issue tracker.
• This is NOT a YouTube, Facebook or Twitch report. These sites MUST be reported by clicking their respective links.
• This is not a support issue or a question. For support, questions, or help, visit /r/uBlockOrigin.
• I performed a cursory search of the issue tracker to avoid opening a duplicate issue.
• The issue is not present after disabling uBO in the browser.
• I checked the documentation to understand that the issue I am reporting is not normal behavior.

I tried to reproduce the issue when...

• uBO is the only extension.
• uBO uses default lists and settings.
• using a new, unmodified browser profile.

Description

I have two JSON filters which work on their own

www.pixiv.net##+js(json-edit-fetch-response, v2:$.body.illusts)
www.pixiv.net##+js(json-edit-fetch-response, v2:$.body.manga)

In the JSONPath tool, if I combine said filters together with brackets it appears to work

v2:$.body.['manga','illusts']

However, if I add this combined expression as a filter it has no effect on the page.

www.pixiv.net##+js(json-edit-fetch-response, v2:$.body.['manga','illusts'])

(It's worth noting an online evaluator lists the bracketed version as invalid JSONPath.)

A specific URL where the issue occurs.

https://www.pixiv.net/en/users/120961088

Steps to Reproduce

1. Open JSONPath tool.
2. Enter JSON Data from gist.
3. Input expression v2:$.body.['manga','illusts']. Observe that results are filtered.
4. Add filter for www.pixiv.net##+js(json-edit-fetch-response, v2:$.body.['manga','illusts'])
5. Go to https://www.pixiv.net/en/users/120961088. Observe that items are filtered.

Expected behavior

The results from the JSONPath tool match the results I see on the page. In other words, either

Option A: The JSONPath tool shows v2:$.body.['manga','illusts'] as an invalid filter.

Option B: Images on the linked URL are filtered, as indicated by the JSONPath tool.

Troubleshooting information

uBlock Origin: 1.72.0
Chromium: 150
filterset (summary):
 network: 181105
 cosmetic: 43260
 scriptlet: 36329
 html: 0
listset (total-discarded, last-updated):
 added:
  https://raw.githubusercontent.com/Stevoisiak/Annoyance-Blocklist/refs/heads/main/annoyance-blocklist.txt: 59-0, 2d.6h.22m
 default:
  user-filters: 1-0, never
  ublock-filters: 51859-87, 2h.46m Δ
  ublock-badware: 10270-27, 2h.46m Δ
  ublock-privacy: 4070-4, 2h.46m Δ
  ublock-unbreak: 2776-1, 2h.46m Δ
  ublock-quick-fixes: 468-0, 2h.46m Δ
  easylist: 85129-485, 2h.46m Δ
  easyprivacy: 55927-713, 2h.46m Δ
  urlhaus-1: 48080-11, 3h.46m
  plowe-0: 3513-0, 4d.5h.45m
filterset (user): [array of 1 redacted]
switchRuleset:
 added: [array of 1 redacted]
userSettings: [none]
hiddenSettings: [none]
supportStats:
 allReadyAfter: 910 ms (selfie)
 maxAssetCacheWait: 200 ms
 cacheBackend: indexedDB

[krystian3w]

Maybe in that way:

• old/ancient school

  www.pixiv.net##+js(json-edit-fetch-response, v2:$.body.['manga'\,'illusts'])

• in the style of the "AdGuard" school

  www.pixiv.net##+js(json-edit-fetch-response, "v2:$.body.['manga','illusts']")
  www.pixiv.net##+js(json-edit-fetch-response, `v2:$.body.['manga','illusts']`)

In short, uBo is comma sensitive, and everything after manga became an second/expensive scriptlet parameter (both invalid; first due bad ending and second was not so-called vararg).
It's best to check whether the parameter underline doesn't break off in the "middle" (when we have good eyesight without any complicated defects) - in uBo linter (view list mode or my filters tab).

I don't know if gorhill is willing to improve the parser since we have the quote, as a last resort we can add the quote with the ` characters so that we don't have to mess with entities when using both quoting formats, and the regex was unavailable.

---

BTW seems duplicate of reply #4033 (reply in thread) in discussion.

[stephenhawk8054]

www.pixiv.net##+js(json-edit-fetch-response, v2:$.body.['manga','illusts'])

You forgot to escape comma or quote around the v2:$.body.['manga','illusts']

[krystian3w]

No, they simply expected that the square brackets protect the comma.

[gorhill]

However, if I add this combined expression as a filter it has no effect on the page.

There is a comma in your query, you need to quote your query to ensure it's treated as a single parameter. Since the query already contains ', use double quote:

www.pixiv.net##+js(json-edit-fetch-response, "v2:$.body.['manga','illusts']")

Note that uBO visually separates parameters with an underline when the line is active, to make it clear that maybe some quoting is needed:

I do intend to bring the same visuals to uBOL.

---

I don't know if gorhill is willing to improve the parser since we have the quote

I am not, because the parser doesn't have intimate knowledge that some parameters should be interpreted as a string or something else like a query -- all parameters are parsed as string, and the scriptlets themselves interpret those strings as they wish.

[stephenhawk8054]

@gorhill Is it possible to have different colors for each query? Sometimes it's a bit difficult to see whether there's a comma for long filters.

[gorhill]

It's worth noting an online evaluator lists the bracketed version as invalid JSONPath

Yes, because there is an extraneous .:

$.body.['manga','illusts']

Should be:

$.body['manga','illusts']

uBO's JSONPath should also error there, I will look for a fix.

[gorhill]

Is it possible to have different colors for each query

It's pure CSS, I can't think of how the color would change with the parameter position. I could make the underline darker when hovering with the mouse cursor.

[stephenhawk8054]

Hmm... How about a different color when hovering?

[Stevoisiak]

You forgot to escape comma or quote around the v2:$.body.['manga','illusts']

Whoops.

Yes, because there is an extraneous .

Double whoops, meant to file that as a separate bug report.

On the note of expressions that work in uBO but not in the JSONPath evaluator, quotes inside brackets seem to be optional in uBO. IE: v2:$.body[illusts].

[Stevoisiak]

Initial issue invalid due to missing quotation marks in query. Follow-up issue of queries being valid in uBO but not evaluator resolved by commits making RFC9535 compliance more strict. Closing.