-
-
Notifications
You must be signed in to change notification settings - Fork 4
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
[FAQ] Open conflicts with VSCode default configuration #66
Labels
question
Further information is requested
Comments
phoenisx
added
question
Further information is requested
and removed
bug
Something isn't working
labels
Sep 3, 2022
If someone knows a solution to any of the conflicts mentioned above, please add a comment for visibility. 🙏🏽 |
This was referenced Sep 4, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This issue keeps a track of all the conflicting behaviour between this extension and VSCode, which are unsolvable or hard to resolve.
Variable duplicates in the same file.
If in a single CSS source file, there are no duplicates, this extension will not show any duplicates. If somehow you do see duplicates, it's possible due to a conflict with VSCode's internal support for CSS variables.
Updating editor settings used to work, but during my recent development, it stopped working. Since VSCode v1.70 or v1.71 no matter what configuration I change, variables defined in the same CSS file always get shown in autocomplete list making them duplicates.
--
trigger does not open the autocomplete dropdownThis is not a bug. Pressing
-
will open the autocomplete list. If it doesn't, pressESC
and press-
again when writing a CSS declaration.In cases where the autocomplete list was already opened due to VSCode or some other extensions, there are chances that CSS variable property names are getting filtered out and are not getting displayed.
You can find a detailed discussion regarding this here: microsoft/vscode-extension-samples#335 (comment)
The text was updated successfully, but these errors were encountered: