Does this issue occur when all extensions are disabled?: No - debugging requires plugins.

• VS Code Version: 1.88.1
• OS Version: MacOS

Steps to Reproduce:

1. Use a debug adapter that applies a deemphasize presentation hint to the top StackFrame of a thread.
2. Observe that VSCode still selects that frame for focus if a stop event is issued for that thread.

Although it isn't part of the DAP, code in the CallStackView envisions the possibility that a stack frame could have a presentation hint deemphasize, in which case it treats that frame the same as if its source had the presentation hint deemphasize, where that value is part of the DAP. However, in the code that selects the top stack frame of a given thread, only the source is checked for the deemphasize presentation hint, leading to the possibility that a frame that is 'deemphasized' according to the CallStackView is nevertheless selected for highlighting, and its source focused, when the debugger signals a stop on that thread.