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
A shake animation to signify errors is a terrible and annoying invention by Apple. All it does to the user experience is rubbing an error into the user's face. The user has enough reason to be annoyed by the occurrence of an error; there is no need to rub an error into users' faces.
How likely is a user to think "Thank you for making an error appear aesthetic, this surely helps me solving it." ?
A red box containing a text such as "invalid file type" or "file is too large" is more than enough to communicate to the user what is wrong. There is no need for a shake to rub it into the user's face.
Reproduction
The shake animation can be reproduced by uploading an invalid file type, such as a 3GP file to a FilePond form which is only configured to accept MP4 files.
I know, the shake animation can be manually disabled by modifying the CSS, which can be done both server-side by the site operator and client-side by the user. However, the user needs to do this on each computer for each website individually, and most site operators don't touch the CSS bundled with FilePond.
Each time I use a new site with FilePond or on a different computer where I have not added the shake-disabling CSS, I realize I forgot that it existed.
Environment
This bug occurs on any computer with any browser that is recent enough to support FilePond.
The text was updated successfully, but these errors were encountered:
Personally I like it, in forms it attracts the user's attention to what is in error, sometimes just a red text is not visible enough. Our vision is based on movement
Is there an existing issue for this?
Have you updated FilePond and its plugins?
Describe the bug
A shake animation to signify errors is a terrible and annoying invention by Apple. All it does to the user experience is rubbing an error into the user's face. The user has enough reason to be annoyed by the occurrence of an error; there is no need to rub an error into users' faces.
How likely is a user to think "Thank you for making an error appear aesthetic, this surely helps me solving it." ?
A red box containing a text such as "invalid file type" or "file is too large" is more than enough to communicate to the user what is wrong. There is no need for a shake to rub it into the user's face.
Reproduction
The shake animation can be reproduced by uploading an invalid file type, such as a 3GP file to a FilePond form which is only configured to accept MP4 files.
I know, the shake animation can be manually disabled by modifying the CSS, which can be done both server-side by the site operator and client-side by the user. However, the user needs to do this on each computer for each website individually, and most site operators don't touch the CSS bundled with FilePond.
Each time I use a new site with FilePond or on a different computer where I have not added the shake-disabling CSS, I realize I forgot that it existed.
Environment
This bug occurs on any computer with any browser that is recent enough to support FilePond.
The text was updated successfully, but these errors were encountered: