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

Open dialog cuts off some files #336

Closed
nol166 opened this issue Mar 25, 2019 · 3 comments
Closed

Open dialog cuts off some files #336

nol166 opened this issue Mar 25, 2019 · 3 comments
Labels
bug Something isn't working

Comments

@nol166
Copy link
Contributor

nol166 commented Mar 25, 2019

  • code-server version: running directly from repo, latest pull
  • OS Version: macOS

Description

The open dialog seems to cut off the filename at the end of the list

Steps to Reproduce

  1. Click file - open workspace
  2. Select a folder with a lot of files/directories
  3. See cutoff at the bottom

Screenshot

Screen Shot 2019-03-25 at 4 29 43 PM

@nol166 nol166 added the bug Something isn't working label Mar 25, 2019
@nol166
Copy link
Contributor Author

nol166 commented Mar 25, 2019

moved to frontend repo

@nol166 nol166 closed this as completed Mar 25, 2019
@cathook
Copy link

cathook commented Jun 3, 2019

I encountered the same issue too. After a bit survey, I think the root cause is that in packages/vscode/src/dailog.ts,Dailog class asks the UI widget to resolve the height of the scroll-able area at the wrong time. When it calls this.entryList.layout() at line 318, path is still empty so the height of the corresponding element is zero. After path is resolved, the element height becomes 28px and the height of the scroll-able area becomes 28px smaller, which is misaligned with the state the UI widget recorded.

One simple solution is to move line 318 to line 393 where path is just assigned. Not sure if there's better way.

Also, just curious, what's the frontend repo?

code-asher added a commit that referenced this issue Jun 7, 2019
@code-asher
Copy link
Member

Thanks for the excellent diagnosis! I've just committed the fix.

Our frontend repository holds the coder.com website; I think this may have been mistakenly moved there.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants