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

[Bug]: vscode_vibrancy.imports not works #33

Closed
1 task done
Rey-Wang opened this issue Oct 14, 2022 · 4 comments
Closed
1 task done

[Bug]: vscode_vibrancy.imports not works #33

Rey-Wang opened this issue Oct 14, 2022 · 4 comments
Labels
bug Something isn't working

Comments

@Rey-Wang
Copy link

Is there an existing issue for this?

  • I have searched the existing issues

Current Behavior

I override some style in a custom css file, but not works

.monaco-list.settings-toc-tree .monaco-list-row.selected,
.monaco-list.settings-toc-tree .monaco-list-row.focused,
.monaco-list .monaco-list-row.selected,
.monaco-list.settings-toc-tree:not(.drop-target) .monaco-list-row:hover:not(.selected):not(.focused) {
  background: #528bff69 !important;
}

image

configuration:

  "vscode_vibrancy.imports": [
    "/Users/reywang/Documents/workHelpers/plugin-config/vscode_vibrancy_custom.css"
  ]

Expected Behavior

image

background color should be red

Steps To Reproduce

No response

Environment

- OS: MacOS Monterey 12.4
- VSCode: Version: 1.72.2 (Universal)
- Extension:Vibrancy Continued v1.1.7

Anything else?

No response

@Rey-Wang Rey-Wang added bug Something isn't working triage Cause of the issue needs to be triaged labels Oct 14, 2022
@illixion illixion removed the triage Cause of the issue needs to be triaged label Oct 14, 2022
@illixion
Copy link
Owner

Thanks for the report, found the issue to have been caused by CSP, just pushed an update that should fix it. Feel free to reopen if you still encounter this issue.

@Rey-Wang
Copy link
Author

@illixion which version would contain this fix?

@Rey-Wang
Copy link
Author

Rey-Wang commented Oct 18, 2022

@illixion for v1.1.8, still not works for me, should I reopen this issue? seems like it could not resolve the path
image

@illixion
Copy link
Owner

Yes, v1.1.8 is the updated version. This error means that the extension couldn't read the file contents of your CSS file, make sure that the path is correct and is accessible. Also, make sure that VSCode is allowed to access the Documents folder through macOS privacy settings.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants