Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support stack info in json-prune scriptlet #2757

Closed
8 tasks done
Yuki2718 opened this issue Jul 27, 2023 · 0 comments
Closed
8 tasks done

Support stack info in json-prune scriptlet #2757

Yuki2718 opened this issue Jul 27, 2023 · 0 comments
Labels
enhancement New feature or request fixed issue has been addressed

Comments

@Yuki2718
Copy link

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 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

See AG docs

A specific URL where the issue occurs.

https://www.youtube.com/watch?v=V6DDAZUgtQs

Steps to Reproduce

NA

Expected behavior

json-prune should support stack info like aost

Actual behavior

Not and it's problematic if a site uses bait Renponse.json()

uBO version

1.51.1b2

Browser name and version

Chrome 114.0.5735.248

Operating System and version

Windows 10

@gwarser gwarser added the enhancement New feature or request label Jul 27, 2023
gorhill added a commit to gorhill/uBlock that referenced this issue Jul 27, 2023
@uBlock-user uBlock-user added the fixed issue has been addressed label Jul 28, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request fixed issue has been addressed
Projects
None yet
Development

No branches or pull requests

3 participants