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

va-file-input component error handling behavior #2813

Open
1 of 6 tasks
rmessina1010 opened this issue May 14, 2024 · 0 comments
Open
1 of 6 tasks

va-file-input component error handling behavior #2813

rmessina1010 opened this issue May 14, 2024 · 0 comments
Labels
bug Something isn't working platform-design-system-team

Comments

@rmessina1010
Copy link
Contributor

rmessina1010 commented May 14, 2024

Bug Report

  • I’ve searched for any related issues and avoided creating a duplicate issue.

What happened

During a conversation with @danbrady we noticed that the Error variant of va-file-inputs still allows a file to go through, which is not the expected behavior.
Screenshot 2024-05-14 at 5 09 51 PM

What I expected to happen

Screenshot 2024-05-14 at 4 59 22 PM

Instead the file input should display the message, but not the file.

Reproducing

For this example I used storybook

Steps to reproduce:

  1. Got to Storybook, local or otherwise
  2. Select the va-file-input story
  3. Select Error Message
  4. Note State ( error message, red highlight, etc)
  5. Upload file ( notd the file is now like default state of va-file-input after upload)

Urgency

How urgent is this request? Please select the appropriate option below and/or provide details

  • This bug is blocking work currently in progress
  • This bug is affecting work currently in progress but we have a workaround
  • This bug is blocking work planned within the next few sprints
  • This bug is not blocking any work
  • Other

Details

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working platform-design-system-team
Projects
None yet
Development

No branches or pull requests

1 participant