Skip to content
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

Terminal Scroll bar appears in the middle #91135

Closed
goxr3plus opened this issue Feb 21, 2020 · 11 comments
Closed

Terminal Scroll bar appears in the middle #91135

goxr3plus opened this issue Feb 21, 2020 · 11 comments
Assignees
Labels
bug Issue identified by VS Code Team member as probable bug terminal Integrated terminal issues verified Verification succeeded
Milestone

Comments

@goxr3plus
Copy link

goxr3plus commented Feb 21, 2020

Gif attached below :

2020-02-21_11-37-58

Also sometimes when i opper two terminals side by side and i close the second , the first one doesn't resize properly .

image

Version: 1.43.0-insider (system setup)
Commit: e6a45f4
Date: 2020-02-21T05:42:20.536Z
Electron: 7.1.11
Chrome: 78.0.3904.130
Node.js: 12.8.1
V8: 7.8.279.23-electron.0
OS: Windows_NT x64 10.0.18363

@gjsjohnmurray
Copy link
Contributor

Does this also occur if you run from command line and disable GPU?

code --disable-gpu

@IllusionMH
Copy link
Contributor

This might be related to the fact that after I hide/show bottom panel there is difference in width of div.terminal.xterm

Fresh terminal in bottom panel
image
Click hide panel or switch to any other tab in panel and show terminal again
image

Which might explain issue with wrong outline in #90568 (and issues that I had when sometimes input line had line breaks early)

It looks funnier immediately after I switch from experimentalWebgl renderer to auto and terminal is hot-reloaded.
image
(after hot reload of renderer I also see that in this case I also see that .split-view-view.visible will change it width, but doesn't happen in case described above)

VS Code version: Code - Insiders 1.43.0-insider (e6a45f4, 2020-02-21T05:42:20.536Z)
OS version: Windows_NT x64 10.0.18363

System Info
Item Value
CPUs Intel(R) Core(TM) i7-8700 CPU @ 3.20GHz (12 x 3192)
GPU Status 2d_canvas: enabled
flash_3d: enabled
flash_stage3d: enabled
flash_stage3d_baseline: enabled
gpu_compositing: enabled
multiple_raster_threads: enabled_on
oop_rasterization: disabled_off
protected_video_decode: enabled
rasterization: enabled
skia_renderer: disabled_off_ok
video_decode: enabled
viz_display_compositor: enabled_on
viz_hit_test_surface_layer: disabled_off_ok
webgl: enabled
webgl2: enabled
Load (avg) undefined
Memory (System) 31.72GB (11.59GB free)
Process Argv
Screen Reader no
VM 0%
Extensions: none

@Tyriar Tyriar added bug Issue identified by VS Code Team member as probable bug terminal Integrated terminal issues upstream Issue identified as 'upstream' component related (exists outside of VS Code) labels Feb 21, 2020
@Tyriar Tyriar added this to the Backlog milestone Feb 21, 2020
@Tyriar
Copy link
Member

Tyriar commented Feb 21, 2020

I suspect a race where viewport doesn't update when resize is fired multiple times in quick succession.

@Tyriar
Copy link
Member

Tyriar commented Feb 21, 2020

@sbatten I think the workbench view refactor caused this and #91119. Are there additional resize events being fired now when the view is hidden?

@Tyriar Tyriar assigned Tyriar and sbatten and unassigned Tyriar Feb 21, 2020
@sbatten
Copy link
Member

sbatten commented Feb 21, 2020

image

initial layout calls, after initial layout no more calls to layout are made with terminal hidden.

/cc @joaomoreno

@IllusionMH
Copy link
Contributor

IllusionMH commented Feb 21, 2020

Not sure if directly related to this one (most likely same as second case in my example with renderer).
If I change editor.font I'll get wrong dimensions for teriminal inside tab. No resizing or hiding tab in this case.
image

@Tyriar
Copy link
Member

Tyriar commented Feb 26, 2020

Solid repro: #91135

@Tyriar Tyriar closed this as completed in 622ddc0 Feb 26, 2020
@Tyriar
Copy link
Member

Tyriar commented Feb 26, 2020

@sbatten please review 622ddc0, also why does layoutBody take height first then width? This is backwards to the standard and results in things like this happening?

@Tyriar Tyriar modified the milestones: Backlog, February 2020 Feb 26, 2020
@Tyriar Tyriar removed the upstream Issue identified as 'upstream' component related (exists outside of VS Code) label Feb 26, 2020
@sbatten
Copy link
Member

sbatten commented Feb 26, 2020

not sure, @joaomoreno implemented it that way a long time ago.

@joaomoreno
Copy link
Member

joaomoreno commented Feb 26, 2020

What standard?

Historically, split views only had one dimension, so it was layout(size). Then, as panels appeared, they were forcibly vertical, so layout(size) would call layoutBody(height). Then, it turns out we needed to pass in width as well, so then layoutBody(height, width) was born. As far as the splitview is concerned, the method is layout(size, orthogonalSize), so we're agnostic there.

@sbatten This can easily be changed to a layoutBody(dimension) at the panel layer.

@Tyriar
Copy link
Member

Tyriar commented Feb 27, 2020

@joaomoreno by standard I mean industry standard that it's almost always (x, y), (width, height), (horizontal, vertical), etc.

@connor4312 connor4312 added the verified Verification succeeded label Feb 28, 2020
@github-actions github-actions bot locked and limited conversation to collaborators Apr 11, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Issue identified by VS Code Team member as probable bug terminal Integrated terminal issues verified Verification succeeded
Projects
None yet
Development

No branches or pull requests

7 participants