Skip to content

Remove "Find Next" and "Find Previous" from Nav dropdown #1243

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

Closed
simranaggarwal1999 opened this issue Jan 18, 2020 · 12 comments · Fixed by #1768
Closed

Remove "Find Next" and "Find Previous" from Nav dropdown #1243

simranaggarwal1999 opened this issue Jan 18, 2020 · 12 comments · Fixed by #1768

Comments

@simranaggarwal1999
Copy link

Nature of issue?

  • 👍 Found a bug
  • 👍 Existing feature enhancement
  • New feature request

Details about the bug:

  • Web browser and version: FireFox

  • Operating System: Windows

  • Steps to reproduce this bug:

  1. Click Edit in navbar
  2. Click Find Next.
  3. Click anywhere on the dialog box that pops up other than the text box.
  4. The dialog box closes.

Feature enhancement details:
I feel the dialog box should not close this way. Also there should be a find button that would start finding in the document according to the letters typed by the user.

@welcome
Copy link

welcome bot commented Jan 18, 2020

Welcome! 👋 Thanks for opening your first issue here! And to ensure the community is able to respond to your issue, be sure to follow the issue template if you haven't already.

@ashu8912
Copy link
Contributor

@simranaggarwal1999 Yes The Find-Next Modal Should Close Only when The close button is clicked.will have to ask @catarak whether she wants this change,if yes will send a pr that fixes this.

@catarak
Copy link
Member

catarak commented Jan 28, 2020

Find next should maybe just open the find dialog? The overall find UX is a little off and should be adjusted to work like other text editors (i.e. VSCode).

Related to #942.

@simranaggarwal1999
Copy link
Author

@catarak I feel Find Next dialog box should find and select the next occurrence of the text specified in the Find dialog box and Find Previous dialog box should find and select the previous occurrence of the text specified in the Find dialog box. Kindly guide me to solve this issue.

@ashu8912
Copy link
Contributor

This is a issue with codemirror the find Next and find Prev both doesn't show the desired behaviour or a behaviour that is not similar to what we expect with editors like vscode when we press these combinations.
I have raised a issue regarding this on the codeMirror repo lets see if they add this feature.
codemirror/codemirror5#6130

@ashu8912
Copy link
Contributor

ashu8912 commented Feb 1, 2020

So The CodeMirror editor doesn't currently supports the behaviour we are thinking of achieving here.

@ashu8912
Copy link
Contributor

ashu8912 commented Feb 1, 2020

@catarak what should we do now with the design should we let it the same for now.

@catarak
Copy link
Member

catarak commented Feb 11, 2021

I think that Find Next and Find Previous should just be removed from the dropdown because it's confusing. The keyboard shortcut overlay lists those shortcuts anyway.

@catarak catarak changed the title The find next and find previous dialog box disappear whenever one clicks on it Remove "Find Next" and "Find Previous" from Nav dropdown Feb 11, 2021
@satyasaibhushan
Copy link
Contributor

Hey @catarak !
I'd like to work on this issue if you simply need to remove the options from the dropdown

@satyasaibhushan
Copy link
Contributor

But, there clearly seems to be a focus issue with the find next and find previous features as sometimes they just go off when clicked on the left part (on the play button or the editor) and they freeze and don't close when clicked on the right part of the screen(on the preview section), which leaves us no option but to refresh the page.
Please look into this!!

@catarak
Copy link
Member

catarak commented Feb 16, 2021

@satyasaibhushan you can go ahead and work on this one!

also, would you mind putting the other issue you're reporting in a separate issue, with steps to reproduce?

@satyasaibhushan
Copy link
Contributor

Hey @catarak,
I hope this closes the issue. Please check if I did anything wrong.
And I will open another issue as you mentioned :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
4 participants