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
Currently, this form error appears at the top. Many of the forms used by the ES UI team are fairly tall, so if there's an error the user won't see the callout unless they scroll up. We've accommodated this by adding another danger callout at the bottom of the screen to let the user know the form contains errors, but this wouldn't be necessary if EuiForm placed its own callout at the bottom.
The text was updated successfully, but these errors were encountered:
EuiForm now has a invalidCallout prop that allows for 'above' | 'none'. We can now easily add the option for 'below' as well.
cchaos
changed the title
[DISCUSS] Consider moving the EuiForm's error callout to the bottom of the form
Add ability to show EuiForm's error callout in the bottom of the form
Sep 18, 2020
cchaos
changed the title
Add ability to show EuiForm's error callout in the bottom of the form
[EuiForm] Add ability to show error callout in the bottom of the form
Sep 20, 2020
shift focus to the validation errors when the box appears, better for screen reader support & can scroll it into view
in addition to above/below, is there a version of the component that returns the validation errors element, allowing it to be placed anywhere in the form
pattern familiarity & recognition - does this or related changes cause confusion for users who are familiar with the existing pattern of always displaying errors at the top
Currently, this form error appears at the top. Many of the forms used by the ES UI team are fairly tall, so if there's an error the user won't see the callout unless they scroll up. We've accommodated this by adding another danger callout at the bottom of the screen to let the user know the form contains errors, but this wouldn't be necessary if
EuiForm
placed its own callout at the bottom.The text was updated successfully, but these errors were encountered: