dotnet / dotnet/aspnetcore

Components.AI: Add accessible stateful attachment chips

Open
#68,413 0 comments 0 reactions 0 assignees View on GitHub
area-blazor cost: M feature-accessibility feature-blazor-builtin-components Priority:0
Dominant language
C#
Stars
38.4k
Forks
10.9k
Avg merge
2d 10h
Merged PRs (30d)
281

Description

### Is your feature request related to a problem? Please describe the problem.

Attachments render as filename text with a remove glyph and do not communicate pending, uploading, ready, or failed state.

### Describe the solution you'd like

Add thumbnail/type-aware attachment chips with pending, uploading, ready, and failed states; list semantics; accessible removal; and predictable focus movement after removal.

### Additional context

Leaf task for #68227 requirements D3 and D8.

Contributor guide

Open the contributing guide

Research direction

Start at the Components.AI attachment rendering entry point and read the parent issue's requirements D3 and D8 in #68227. Trace how attachment states and removal currently work, then verify that chips expose pending, uploading, ready, and failed states, use list semantics, provide accessible removal, and move focus predictably after removal.

Written by the indexing model from the issue text.

Assessment

Tech stack
csharp
Domain
accessibility, frontend
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
58/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.