-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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
fix debug exception height computation #8382
fix debug exception height computation #8382
Conversation
bd359d8
to
607bc1b
Compare
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.
The margin at the bottom is now bigger than the one at the top. Is that intended behavior? According to the screenshot in the ticket it seems to be equal for VS Code. Just wondering 😉 |
@danidoedel I've noticed it too. That's because zone (distance between lines) height is computed by Monaco, but content height is by browser. If it try to match it then with each edit content height grows by 2px which leads to overflow eventually. I guess it is the same issue in VS Code. |
@DoroNahari hm, I cannot reproduce it. Are sure that you are trying Theia from this PR, not Gitpod Theia? on the image below it is a tab without Gitpod logo: @vince-fugnitto @amiramw Could you try to reproduce? |
I verified again using Gitpod and it worked correctly: |
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.
For me it tested successfully. Both these issues are solved now:
- Stripe covering the code.
- When moving to another opened tab the stripe stays.
(in #8344 the second issue was not solved)
There is some difference on behavior comparing to vs code but I think I'm fine with it:
when you resize the browser window to be smaller the stripe height stays the same and the bottom of the stack trace is disappearing. In vs code the stripe height is getting bigger on such resize.
@@ -175,7 +175,7 @@ export class DebugEditorModel implements Disposable { | |||
|
|||
protected async toggleExceptionWidget(): Promise<void> { | |||
const { currentFrame } = this.sessions; | |||
if (!currentFrame) { | |||
if (!currentFrame || !currentFrame.source || currentFrame.source.uri.toString() !== this.uri.toString()) { |
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.
maybe currentFrame?.source?.uri?.toString() !== this.uri.toString()
Signed-off-by: Anton Kosyakov <[email protected]>
607bc1b
to
fee75c2
Compare
@amiramw Could you try again? resizing should be handled as well now |
Resizing is responding well now. 👍 |
@amiramw Could you check please with @DoroNahari as well? If you can do it offline. It is important for me that we don't overlook something. |
LGTM |
Signed-off-by: Anton Kosyakov [email protected]
What it does
How to test
Launch with Node.js
debug configuration to debug itReview checklist
Reminder for reviewers