Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug] Please remove the shaking animation. #948

Open
2 tasks done
HT-7 opened this issue Dec 2, 2023 · 0 comments
Open
2 tasks done

[Bug] Please remove the shaking animation. #948

HT-7 opened this issue Dec 2, 2023 · 0 comments

Comments

@HT-7
Copy link

HT-7 commented Dec 2, 2023

Is there an existing issue for this?

  • I have searched the existing issues

Have you updated FilePond and its plugins?

  • I have 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.

@HT-7 HT-7 added the bug label Dec 2, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants