microsoft
Bracket pair highlight border highlights different brackets to the bracket pair guides
Does this issue occur when all extensions are disabled?: Yes
- VS Code Version: 1.74.0
- OS Version: Windows 11
Steps to Reproduce:
- Place the cursor on the left of an opening bracket or on the right of a closing bracket.
- Notice how the bracket pair highlight border highlights different brackets to the bracket pair guides.
https://user-images.githubusercontent.com/101095063/206406932-70ce5b39-7b20-4f93-81ce-9b59c7375b74.mp4
Afaik this used to be as you suggest, but it would be weird in (...) && (...), then (...)| && (...) would indicate that the first parenthensis group is active.
This feature request is now a candidate for our backlog. The community has 60 days to upvote the issue. If it receives 20 upvotes we will move it to our backlog. If not, we will close it. To learn more about how we handle feature requests, please see our documentation.
Happy Coding!
Afaik this used to be as you suggest, but it would be weird in
(...) && (...), then(...)| && (...)would indicate that the first parenthensis group is active.
Not sure what you mean, could you explain further? You could add a setting so people who don't like it can turn it off.
The active bracket pair guides indicate to which block you are currently adding text/instructions.
When you have a block { console.log(1); }| and the cursor is at |, the block before the cursor is not active, as any text you type will be added outside the block.
I should have said that when the cursor is on the left of an opening bracket or on the right of a closing bracket the bracket pair highlight border should highlight the brackets that the bracket pair guides draw a line between, which are the brackets surrounding the block of code the cursor is in.
This photoshopped screenshot shows what it should look like:
This is what it currently looks like:
This currently happens when there are two closing brackets next to each other, it would make sense for it to always highlight brackets in this way:
Sorry I wasn't clear.
It used to be like that too, but we got a lot of feedback to change it. If you find the issue where this got discussed, please link it from here.
Feel free to create a new feature request about introducing a setting - probably we would accept a PR for that.
The described behavior is how it is expected to work. If you disagree, please explain what is expected and what is not in more detail. See also our issue reporting guidelines.
Happy Coding!