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

The first symbol you type in the Find and Replace dialog is handled incorrectly #7515

Open
kuraga opened this issue Nov 6, 2024 · 2 comments

Comments

@kuraga
Copy link

kuraga commented Nov 6, 2024

Description

The first symbol you type in the Find and Replace dialog is handled incorrectly.

Reproduce

  1. Open Jupyter.
  2. Open an existing notebook.
  3. Press <Ctrl-F>.
  4. The Find and Replace dialog opens.
  5. The Find input is selected.
  6. Press some magic key, say f.

Actual:

  1. The Find input content is (empty).
  2. The content real being found is f.
  3. Press f.
  4. The Find input content is f.
  5. The content real being found is f.

Expected behavior

Expected:

  1. The Find input content is f.
  2. The content real being found is f.
  3. Press f.
  4. The Find input content is ff.
  5. The content real being found is ff.

Context

Don't know:

  • how to reproduce this behavior stable,
  • whether it is known,
  • whether it depends on window manager, etc.
  • Operating System and version: Calculate Linux (Gentoo-based)
  • Browser and version: Chromium 129.0.6668.100, 64 bit
  • Jupyter Notebook version: 7.2.2
@kuraga kuraga added bug status:Needs Triage Applied to issues that need triage labels Nov 6, 2024
@RRosio
Copy link
Collaborator

RRosio commented Nov 12, 2024

Thank you for opening this issue @kuraga! This issue has been reported in the JupyterLab in: jupyterlab/jupyterlab#16928. This would likely be fixed in Notebook once a fix goes in for it in the JupyterLab codebased. I will label it as blocked to signal the need for work to be done in the JupyterLab code.

@RRosio RRosio added status:Blocked and removed status:Needs Triage Applied to issues that need triage labels Nov 12, 2024
@kuraga
Copy link
Author

kuraga commented Nov 12, 2024

Thanks!

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

2 participants