[css] look for variables in all open documents about vscode HOT 9 OPEN

book-keeping note: https://stackoverflow.com/q/78604916/11107541

from vscode.

What's happening is that when the code completion is invoked the first time, textual proposals are shown as the CSS language server has no proposals.
Once there's a color name in the file, the CSS language server shows that color. The textual proposals don't show anymore

• textual proposals uses the contents of all open editors
• the css extension only uses the current document
• the textual proposals are considered a 'fallback' is there's no language server providing any results.

from vscode.

Under what circumstances is this likely to be addressed?

• Without any @imports?
• If the variable-using file @imports the variable-declaring file(s)?
• If some other CSS file @imports them both (or HTML <link>s them both)- the variable-declaring file first?

from vscode.

aeschli, it doesn't seem to matter what the type of property is...for example if I add a property of --myvalue: 32; and then assign the width: var(--myvalue) and further down try to assign the color: var(--xx); it offers me only --myvalue (an integer) and not one of the color properties. Does this fit within the same explenation?

from vscode.

Yes, the css extension doesn't know what type the variable is. It just proposes all variable names that it can find in the current document.
Following imports is currently not planed. But I can look into looking at the contents of all open editors that show CSS files.

from vscode.

Thanks very much for looking into the problem. From my perspective it would seem that displaying all of the properites every time would be very beneficial. Without that functionality, it degrades the usefulness of the custom properties. Instead of Intellisense including those choices each time, it forces me to go back to a long list of properties in 1 or more files each time I want to use one. A more sensible way might be to always show all of the textual proposals and then maybe either order by or highlight those that also already exist in the current document, but having them disappear makes no sense and is not useful at all. Thanks again!

from vscode.

I can look into looking at the contents of all open editors that show CSS files

Would this just be for custom properties declared in a rule with the :root selector? That would be the safer option correctness-wise. Even then, it'd be risking wrong suggestions with shadow DOM involved.

from vscode.

Available variables are only known at runtime, when a rule is matched. Even then it's not wrong to access an undefined variable
So proposing all variables found is what we should do.

from vscode.

I would think it should behave the way it does the first time you use var() ... using it a second or nth time shouldn't change the behaviour, which it now does...consistency is best.

from vscode.