-
Notifications
You must be signed in to change notification settings - Fork 29.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
testing: use a real terminal in test Test Results view #184963
Conversation
src/vs/workbench/contrib/terminal/browser/xterm/xtermTerminal.ts
Outdated
Show resolved
Hide resolved
src/vs/workbench/contrib/terminal/browser/xterm/xtermTerminal.ts
Outdated
Show resolved
Hide resolved
src/vs/workbench/contrib/terminal/browser/xterm/xtermTerminal.ts
Outdated
Show resolved
Hide resolved
9290ea3
to
6dc393c
Compare
6dc393c
to
714e6b6
Compare
bf8bcd3
to
1f3b6d6
Compare
if (e.browserEvent?.defaultPrevented) { | ||
return; | ||
} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What's this change for? Worried about regressions
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
xterm correctly calls .preventDefault() if a scroll event gets handled by the terminal, but this wasn't respected by the editor. This resulted in scrolling within the terminal when it's shown in the inline peek to scroll the editor when it should instead have just scrolled the terminal.
I'm guessing this is the first time we have something in the editor that manually handles scrolling, so this check was missing.
For #151964
Shows test output in a real terminal. Adds a new notion of a 'detached' XtermTerminal instance that's used to show a terminal here. It also wires up a subset of terminal commands to work in the terminal. Currently I have assumed such detached terminals will always be read-only.