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

After refreshing the page, automatically focus on the first file or folder #15980

Open
FoSuCloud opened this issue Mar 13, 2024 · 4 comments
Open

Comments

@FoSuCloud
Copy link
Contributor

FoSuCloud commented Mar 13, 2024

Description

If we are not in the root directory, after refreshing the page, we will automatically focus on the first file or folder.

Reproduce

  1. Click to enter a folder from the root directory
  2. refresh the page

default-file

default folder

Expected behavior

Do not focus on the first file or folder by default after refreshing the page. The black border is too ugly.

Context

  • Operating System and version: macOS 12.2
  • Browser and version:Chrome 122
  • JupyterLab version: jupyterlab 4.1.2
Troubleshoot Output
Paste the output from running `jupyter troubleshoot` from the command line here.
You may want to sanitize the paths in the output.
Command Line Output
Paste the output from your command line running `jupyter lab` here, use `--debug` if possible.
Browser Output
Paste the output from your browser Javascript console here, if applicable.
@FoSuCloud FoSuCloud added bug status:Needs Triage Applied to new issues that need triage pkg:filebrowser labels Mar 13, 2024
@krassowski
Copy link
Member

This should be alleviated by #15860. I just realised this was not backported to 4.1.x, fixing this now.

@JasonWeill
Copy link
Contributor

@FoSuCloud Do you still see this behavior in the 4.1.5 release?

@FoSuCloud
Copy link
Contributor Author

@FoSuCloud Do you still see this behavior in the 4.1.5 release?

Yes, I can still see this problem in version 4.1.5

@FoSuCloud
Copy link
Contributor Author

This should be alleviated by #15860. I just realised this was not backported to 4.1.x, fixing this now.

It seems that the #15860 does not solve this problem

@JasonWeill JasonWeill removed the status:Needs Triage Applied to new issues that need triage label Mar 20, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants