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
This is a re-open of #43402. (The conversation for the prior issue is locked.) It is worth looking into whether the extension system supports implementing this feature effectively. In the year plus since that issue was created, no one has created a working extension to implement the feature.
There is an extension, Auto Rename Tag, that tries to do this, but it only works if you type slowly (formulahendry/vscode-auto-rename-tag#62) and has lots of issues reported for high CPU load. I don't know if it's a matter of the developer knowing how to use the VS Code API correctly or the API not supporting well what the extension is trying to do.
This issue requests that the VS Code team look into (1) making sure a suitable extension is practical to develop and (2) making such an extension available.
The text was updated successfully, but these errors were encountered:
#76619 is about CSS and looks to me to be distinct from this issue, which is about HTML close tags (which CSS doesn't even have). @aechan Can you elaborate on the dup?
This is a re-open of #43402. (The conversation for the prior issue is locked.) It is worth looking into whether the extension system supports implementing this feature effectively. In the year plus since that issue was created, no one has created a working extension to implement the feature.
There is an extension, Auto Rename Tag, that tries to do this, but it only works if you type slowly (formulahendry/vscode-auto-rename-tag#62) and has lots of issues reported for high CPU load. I don't know if it's a matter of the developer knowing how to use the VS Code API correctly or the API not supporting well what the extension is trying to do.
This issue requests that the VS Code team look into (1) making sure a suitable extension is practical to develop and (2) making such an extension available.
The text was updated successfully, but these errors were encountered: