Consider not jumping to a file when clicking on a style property

I would suggest aligning the behavior of clicking on a style property in the extension with the behavior of the developer tools in the browser. Currently, the behavior seems to be different: in the extension the CSS file is directly opened, while in the browser this does not happen. I think it's more useful to have the browser behavior, because I often use the extension to do some style tweaks / experiments without necessarily wanting to jump to the corresponding file. Furthermore, when using WSL I get some error messages every time I click a style property, because the file can't be opened. This would also be avoided if the extension doesn't immediately try to open the file.

I previously raised this suggestion (#259) and it was implemented. However, in the current version (2.1.3) of the extension the old behavior is back.

Previous suggestions that were implemented:

• when clicking on a style property, don't jump to the file
• when clicking on the filename, do jump to the file
• when control-clicking on a selector, style property or value, do jump to the corresponding file and line

Is it possible to re-introduce this behavior? Or alternatively, provide a configuration setting for this behavior or a configuration setting to turn off every jump-to-file behavior?

Reproduce clicking a style property in the VSCode extension and compare it with the browser developer tools behavior described in the issue. No files or tests are named; done means style-property clicks no longer open a CSS file, while filename clicks and control-click navigation retain their stated behavior.