-
Notifications
You must be signed in to change notification settings - Fork 613
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
Upgrade xterm v3.12.0 to v4.10.0 #8260
Conversation
frontend/packages/console-shared/src/utils/xterm-addon-fullscreen.ts
Outdated
Show resolved
Hide resolved
19b0e79
to
b9361e8
Compare
} | ||
|
||
public dispose(): void { | ||
if (this.terminal && this.terminal.element.classList.contains('fullscreen')) { |
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.
instead of checking for this.terminal
here and below, will it make sense to just have
if (this.terminal && this.terminal.element.classList.contains('fullscreen')) { | |
if (his.terminal?.element?.classList?.contains('fullscreen')) { |
/assign |
|
||
XTerminal.applyAddon(fit); | ||
XTerminal.applyAddon(full); | ||
import { XtermAddonFullscreen } from '@console/shared'; |
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.
Why do we need custom implementation of fullscreen addon? Did xterm remove support for their fullscreen addon?
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.
iirc @sahil143 said they removed this addon. I'm not sure if they replaced or why it was removed though.
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.
Yeah, seems like they removed fullscreen addon - xtermjs/xterm.js#2065 (comment)
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.
Yes, fullscreen addon was removed when addon api changed
/approve |
@sahil143 I found two issues: a) The small one is the "black gap" on the bottom right corner below the scrollbar: update: This issue already exist on the master branch. Would be cool to fix this anyway. Up to you. b) It looks like the page resize depends on the full screen height instead of the window height. I have two scrollbars. The one for the terminal is fine but the other one shows a white space below the terminal: Peek.2021-03-10.09-35.mp4update: Could reproduce this also on the latest Chrome and Firefox version. This does not happen on master. See comments below. |
/retest |
@jerolimov I'm not able to reproduce this on chrome version 89. Which version are you on? |
I was able to reproduce in chrome 88 but then I upgraded to 89 and can't see dual scroll anymore however on firefox I can on |
I tested this also on Chrome 88 where this happen. I updated now to Chrome 89 and it works here. Don't know if we want fix this anyway? As mentioned by Jai it happens also on the latest Firefox ESR version. Hmm? |
I tried on Firefox 87 as well not able to reproduce it. |
@sahil143 I can reproduce this also on (latest stable) 86.0. But it does not happen always! It only happens here if I first added some content (many Peek.2021-03-10.12-57.mp4Here the same issue with (latest) Chrome 89: Peek.2021-03-10.12-59.mp4I tested this also again on the master branch and could not reproduce this here. My problem A with the black border below the scrollable area exists already on the master branch. Tested with master: Peek.2021-03-10.13-05.mp4 |
Took some time but finally figured out the issue. The main issue here is with the |
There is already an open issue on xterm.js repo with similar behaviour xtermjs/xterm.js#3065 |
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.
There is already an open issue on xterm.js repo with similar behaviour xtermjs/xterm.js#3065
Would be cool to fix it there and keep this bug in mind. I will create a new issue for this so that we can upgrade the dependency now for your depending work.
/lgtm
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: christianvogt, jerolimov, sahil143 The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Fixes: https://issues.redhat.com/browse/ODC-5547
Analysis / Root cause: To send commands programmatically to the terminal we need feature(addons) from the xterm.js v4.10.0
Solution Description: upgrade xterm version
Screen shots / Gifs for design review: No UI changes
Unit test coverage report:
Test setup:
Browser conformance: