You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When attempting to rename an HTML tag through F2 rename key, vscode shows a tooltip as seen below:
Expected behaviour
The vscode allows renaming the tag, as usual in HTML files with built-in HTML language features.
Additional info
I am sure this bug is relative to the Volar extension as everything works as expected if the extension is disabled.
I am using takeover mode with Volar, but not all my project is within a build system, so I have plain HTML files.
Whenever I open an HTML file, I get on the breadcrumbs that "HTML Language Features" sub-entry (see below), side-by-side with a "Vue Language Feature (Volar)" which, to my understanding, should not happen in plain HTML files: why is Volar attempting to interfere in this file, as it is not a Vue SFC?
Environment
VS Code: v1.68.1
Volar: v0.38.2
OS: Windows 11 Version 10.0.22000 Build 22000
The text was updated successfully, but these errors were encountered:
Renaming tags is working for me in html files while Volar is enabled. I also have the "HTML Lanugage Features" in the breadcrumbs.
Could you open a terminal and look into the output of extensions? Maybe there is some kind of error message in there.
Issue
When attempting to rename an HTML tag through F2 rename key, vscode shows a tooltip as seen below:
Expected behaviour
The vscode allows renaming the tag, as usual in HTML files with built-in HTML language features.
Additional info
I am sure this bug is relative to the Volar extension as everything works as expected if the extension is disabled.
I am using takeover mode with Volar, but not all my project is within a build system, so I have plain HTML files.
Whenever I open an HTML file, I get on the breadcrumbs that "HTML Language Features" sub-entry (see below), side-by-side with a "Vue Language Feature (Volar)" which, to my understanding, should not happen in plain HTML files: why is Volar attempting to interfere in this file, as it is not a Vue SFC?
Environment
The text was updated successfully, but these errors were encountered: