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
I think clicking that icon should do the same as pressing the enter key. I thought my instance was broken for quite a while until I realized it actually expects the user to press the enter key.
I'm logging this as a bug because if this isn't a broken button, I don't know why it was put there in the first place
The text was updated successfully, but these errors were encountered:
This for sure is not a bug. It simply visualizes what this input field is supposed to do: add a Task. Besides, why should a submit/create button be on the left and provide no feedback when hovered, unlike every other button in the app? And if you ever used the Google search engine, you might be used to it: The magnifying glass icon on the left just does nothing and is not a button.
But I agree, that we could show a submit button on the right of the input field, similar to how it's done in the new TextField component of nextcloud/vue:
raimund-schluessler
changed the title
[Bug] Make the "+" icon actually add a task.
[Feature Request] Make the "+" icon actually add a task.
Aug 16, 2022
raimund-schluessler
changed the title
[Feature Request] Make the "+" icon actually add a task.
[Feature Request] Show submit button on the right of new Task input field
Aug 19, 2022
My two cents: Google tries to avoid confusion like OP's: They show the magnifying glass icon as slightly darker than the input's font color, the same color as the input field's borders. This makes it more clear that the icon is not interactive. Maybe the same could be done here, too.
I think clicking that icon should do the same as pressing the enter key. I thought my instance was broken for quite a while until I realized it actually expects the user to press the enter key.
I'm logging this as a bug because if this isn't a broken button, I don't know why it was put there in the first place
The text was updated successfully, but these errors were encountered: