-
-
Notifications
You must be signed in to change notification settings - Fork 2.6k
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Add requirement Id to ui-recommendations.md
- Loading branch information
Showing
1 changed file
with
12 additions
and
4 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -8,19 +8,27 @@ parent: Code Howtos | |
* For a usual form, place the label above the text field | ||
* If the user uses the form often to edit fields, then it might make sense to switch to left-aligned labels | ||
|
||
## Designing GUI Confirmation dialogs | ||
## Designing GUI Confirmation Dialogs | ||
|
||
1. Avoid asking questions | ||
2. Be as concise as possible | ||
3. Identify the item at risk | ||
4. Name your buttons for the actions | ||
|
||
More information: [http://ux.stackexchange.com/a/768](http://ux.stackexchange.com/a/768) | ||
More information: | ||
|
||
- [StackOverflow: What are some alternatives to the phrase "Are you sure you want to XYZ" in confirmation dialogs?](https://ux.stackexchange.com/q/756/93436). | ||
Check failure on line 20 in docs/code-howtos/ui-recommendations.md GitHub Actions / MarkdownUnordered list style
|
||
- JabRef issue discussing Yes/No/Cancel: [koppor#149](https://github.com/koppor/jabref/issues/149). | ||
Check failure on line 21 in docs/code-howtos/ui-recommendations.md GitHub Actions / MarkdownUnordered list style
|
||
|
||
### Name your buttons for the actions | ||
`req~ui.dialogs.confirmation.naming~1` | ||
|
||
## Form validation | ||
|
||
* Only validate input after leaving the field (or after the user stopped typing for some time) | ||
* The user shouldn't be able to submit the form if there are errors | ||
* However, disabling the submit button in case there are errors is also not optimal. Instead, clicking the submit button should highlight the errors. | ||
* Empty required files shouldn't be marked as invalid until the user a) tries to submit the form or b) focused the field, deleted it contents and then left the field (see [Example](https://www.w3schools.com/tags/tryit.asp?filename=tryhtml5_input_required) | ||
* Ideally, the error message should be shown below the text field and not as a tooltip (so that users quickly understand what's the problem). For example as here [in Boostrap](https://mdbootstrap.com/docs/jquery/forms/validation/?#custom-styles) | ||
* Empty required files shouldn't be marked as invalid until the user a) tries to submit the form or b) focused the field, deleted it contents and then left the field (see [Example](https://www.w3schools.com/tags/tryit.asp?filename=tryhtml5_input_required)() | ||
* Ideally, the error message should be shown below the text field and not as a tooltip (so that users quickly understand what's the problem). For example as [in Boostrap](https://mdbootstrap.com/docs/jquery/forms/validation/?#custom-styles). | ||
|
||
<!-- markdownlint-disable-file MD022 --> |