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
XPATH, "//input[@type='text' and @placeholder='Project title']"
It would be help to add an Enter key to save an edit. Currently, I think I needed a Tab key. Would be great to have both.
For this name input on the Settings page:
XPATH, //input[@type='text' and @placeholder='Enter title of project here']
It might be helpful to also add an Enter. For now it saves the form, which may also be a desired behavior(?)
For the description input on the Settings page, the Enter key starts a new line.
That's probably an appropriate behavior.
In essence,
on the Name input at the top of the form, Enter seems to do nothing.
On the Settings page in the Name input Enter submits the form.
On the Settings page in the Name input Enter starts a new line.
Three different behaviors. I think the main ask here would be to change the behavior of item 1 above, and then potentially leave the other two as-is. (Another option for the Description is to have the Enter key do a Save, and expect that people won't use a newline in a Description (or accept a Shift-Enter as a new line.) In that case, all three would consistently save the new content via Enter.
The text was updated successfully, but these errors were encountered:
We have plans (#1883 with PR in review) to remove name editing option from header, so it will be clearer in the future. The question is if we should make it clearer that description is multiline with ENTER key not submitting the settings form @pmusaraj ?
We could add a hint, but OTOH, the description is not all that useful to the user (most projects have no description), so the hint seems like an unnecessary addition to the form.
It would be help to add an Enter key to save an edit. Currently, I think I needed a Tab key. Would be great to have both.
It might be helpful to also add an Enter. For now it saves the form, which may also be a desired behavior(?)
That's probably an appropriate behavior.
In essence,
Three different behaviors. I think the main ask here would be to change the behavior of item 1 above, and then potentially leave the other two as-is. (Another option for the Description is to have the Enter key do a Save, and expect that people won't use a newline in a Description (or accept a Shift-Enter as a new line.) In that case, all three would consistently save the new content via Enter.
The text was updated successfully, but these errors were encountered: