| Wiki Markup |
|---|
h2. Story
Magnolia has to show messages related to specific attributes of items in [lists|Definition of terms#list], [trees|Definition of terms#trees] and [grids|Definition of terms#grid]. An example of this is the inline editing in trees, which allows me to change e.g. the page name without having to open the page properties edit dialog first.
For errors, I usually have to fix the error in order to an ongoing operation to complete. Alternatively, I may choose to not fix the problem and cancel the operation entirely. If I cancel the operation, previously stored values are restored, if they exist.
h2. Description of desired behavior
Validation messages inform of a problem caused by an input operation of the user.
If a validation message reports an *error*, it keeps the field with the attribute value editable and only disappears, if the user fixes the problem or cancels editing. If editing is cancelled or the user chooses to leave the context where editing took place (e.g. by closing the browser or switching to a different work area), Magnolia aborts the entire edit operation causing the error. So if the user added a page, but provided no page name, an error message is shown. If the user tries to dismiss the message, it stays forcing the user to provide a page name. If he then quits the browser, the page he attempted to add is not added at all. But if, on the other hand, the user edited a page and cleared the page name, this causes the same error message to appear. If he dismisses the message now, the previously stored value for the page name is restored.
If a validation message reports a *warning* or simply provides additional *information*, the field with the attribute value is marked and the user has to focus or select it in order to see the associated message. The message does not have to be dismissed and does not cancel any ongoing operation. It disappears, however, if the focus or selection is moved away from the field.
h2. Mockups
{mockup} |
Story
Magnolia has to show messages related to specific attributes of items in lists, trees and grids. An example of this is the inline editing in trees, which allows me to change e.g. the page name without having to open the page properties edit dialog first.
For errors, I usually have to fix the error in order to an ongoing operation to complete. Alternatively, I may choose to not fix the problem and cancel the operation entirely. If I cancel the operation, previously stored values are restored, if they exist.
Description of desired behavior
Validation messages inform of a problem caused by an input operation of the user.
If a validation message reports an error, it keeps the field with the attribute value editable and only disappears, if the user fixes the problem or cancels editing. If editing is cancelled or the user chooses to leave the context where editing took place (e.g. by closing the browser or switching to a different work area), Magnolia aborts the entire edit operation causing the error. So if the user added a page, but provided no page name, an error message is shown. If the user tries to dismiss the message, it stays forcing the user to provide a page name. If he then quits the browser, the page he attempted to add is not added at all. But if, on the other hand, the user edited a page and cleared the page name, this causes the same error message to appear. If he dismisses the message now, the previously stored value for the page name is restored.
If a validation message reports a warning or simply provides additional information, the field with the attribute value is marked and the user has to focus or select it in order to see the associated message. The message does not have to be dismissed and does not cancel any ongoing operation. It disappears, however, if the focus or selection is moved away from the field.
Mockups
...