-
-
Notifications
You must be signed in to change notification settings - Fork 116
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
How to disconnect the field on the new GhostText? #178
Comments
I think that the current method is sufficient... |
@fregante Ideas to disconnect:
|
I like that. Keyboard shortcuts are cheap, as long as I can register an action without setting a default shortcut (so it's up to the user to customize it)
I feel you, the simplicity was good. I wonder if that should be the regular behavior, while still allowing multiple fields by:
However this would mean that the first Activation would work one way, and the next activations would work differently… a bit confusing. |
Makes me wonder if GT should exclusively handle focused fields:
That's it. Simple. No field focused = do nothing. You must select the field first and then you activate GhostText. This should simplify the code too, because there's no more "Focus (another) field to activate" state. Perhaps with an additional behavior:
Full flow chart: https://user-images.githubusercontent.com/1402241/108940258-a2598300-7618-11eb-902f-b704c5a02c5a.png |
This comment has been minimized.
This comment has been minimized.
Right-clicking is a bit awkward and doesn't work when the icon is in a menu on Safari (it used to be the same in Chrome, but they added hamburgers now) I think GhostText should have a minimal UI to allow disconnection. This would appear sticky on the page: The only concern is integrating it with the notifications. Maybe:
|
Originally posted by @subnut in #172 (comment):
Yeah the current disconnection logic isn't super clear. In the previous version you would just click the button again and it would disconnect, but now it just looks for more fields.
So the solution I came up with is to right click the button 😬 or to just close the editor tab (which would make more sense, since you're done with it so you want to go back to the browser)
Does anyone have any suggestions for an intuitive way to disconnect the editor from the browser?
The text was updated successfully, but these errors were encountered: