vscode-vibrancy-continued: [Bug]: Not working on VS Code `v1.78.0`
Is there an existing issue for this?
- I have searched the existing issues
Current Behavior
When executing Enable Vibrancy the process appears to execute successcully but after the restart nothing happens. Looking to the developer console, we have:
Refused to create a TrustedTypePolicy named 'VscodeVibrancy' because it violates the following Content Security Policy directive: "trusted-types amdLoader
cellRendererEditorText
defaultWorkerFactory
diffEditorWidget
diffReview
domLineBreaksComputer
dompurify
editorGhostText
editorViewLayer
notebookRenderer
stickyScrollViewLayer
tokenizeToString
Expected Behavior
Transparency applied to the VS Code Window
Steps To Reproduce
- Update VS Code to
v1.78.0 - Run
Enable Vibrancy - Restart
Environment
Version: 1.78.0
Commit: 252e5463d60e63238250799aef7375787f68b4ee
Date: 2023-05-03T20:09:00.748Z
Browser: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Code/1.78.0 Chrome/108.0.5359.215 Electron/22.4.8 Safari/537.36
Anything else?
No response
About this issue
- Original URL
- State: closed
- Created a year ago
- Reactions: 5
- Comments: 34 (11 by maintainers)
Solution found, the issue was a lot simpler: the meta tag responsible for the CSP was updated, and the regex that was used to update it didn’t account for the new format. I’m updating the relevant code to improve how this is handled and will push an update as soon as that’s done.
Updated version v1.1.15 is now available on the Marketplace, closing as completed.
Seems like the newest version of VSCode restricted CSP even further, so it’s no longer possible to create custom policies to load the necessary resources. I’ll see what can be done about this.
The same problem, I have rolled back to v1.77.3
@Th3Gl0w I installed Vscode via
homebrew, you can read my note to get the details of rollback.