You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 19, 2017. It is now read-only.
I see some small weirdnesses here, but I can't get it into a bad state. In particular, it seems like doing this can cause the underlying input to lose focus, but still have selected text. I can always get the cursor back by just clicking the text though. Is it worse than this? If not, I don't think this should be high priority.
If you have a text in the search bar, it might be easier to click on it to recover the cursor, but if you do not have any text, it is much harder to get the cursor back. To do that, you need to carefully move the mouse to the top of the input line and if you are careful enough, you will see the cursor changes to i beam. Then click the mouse. Otherwise the search bar is dead.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Cmd/Ctrl-f to open the search bar.
Mouse down and drag the mouse a few pixels inside the search bar.
RESULT: Text input cursor disappears and cannot type text in the search bar.
WORKAROUND: Close and reopen the search bar.
The text was updated successfully, but these errors were encountered: