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

Broken Parse Tree Window on VSCode v1.73 #192

Closed
c4lcifer opened this issue Nov 4, 2022 · 1 comment
Closed

Broken Parse Tree Window on VSCode v1.73 #192

c4lcifer opened this issue Nov 4, 2022 · 1 comment
Labels
possible bug Could be a bug

Comments

@c4lcifer
Copy link

c4lcifer commented Nov 4, 2022

i recently updated VScode from 1.67.2 to latest 1.73 on Ubuntu 22.04

After this upgrade the graphs were no longer drawn. It would still open the parse tree window, but it would stay blank.
I am using antlr4-python-runtime 4.9.3 and vscode-antlr4 2.3.0

Only a reinstall of vscode 1.67.2 fixed the issue for me. I did not test any other VSCode versions

@mike-lischke
Copy link
Owner

This is the result of an ever ongoing battle for browser security:

index.html?id=e9cf786f-f809-419b-a31d-a992fcabf91c&origin=f0aaeb52-265d-411a-bb60-1811d7564ae5&swVersion=4&extensionId=mike-lischke.vscode-antlr4&platform=electron&vscode-resource-base-authority=vscode-resource.vscode-cdn.net&parentOrigin=vscode-file%3A%2F%2Fvscode-app:969 Refused to load the script 'vscode-resource:/Users/mike/.vscode/extensions/mike-lischke.vscode-antlr4-2.3.0/node_modules/d3/dist/d3.js' because it violates the following Content Security Policy directive: "script-src 'self' https://*.vscode-cdn.net 'self' 'unsafe-inline' 'unsafe-eval' https:". Note that 'script-src-elem' was not explicitly set, so 'script-src' is used as a fallback.

@mike-lischke mike-lischke added the possible bug Could be a bug label Nov 4, 2022
mike-lischke added a commit that referenced this issue Nov 6, 2022
Reworked content security policy to have stricter settings and correctly specify allowed scripts (via nonces).
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
possible bug Could be a bug
Projects
None yet
Development

No branches or pull requests

2 participants