Components.AI media rendering
- Dominant language
- C#
- Stars
- 38.4k
- Forks
- 10.9k
- Avg merge
- 2d 6h
- Merged PRs (30d)
- 290
Description
### Is your feature request related to a problem? Please describe the problem.
Media is rendered through hand-written elements and data URIs, inline rich media is dropped, and loading/failure behavior can destabilize virtualized content.
### Describe the solution you'd like
Track standalone and rich-node media integration through `Microsoft.AspNetCore.Components.Media`, including accessible metadata, downloads, sizing, loading, failure, and image affordances.
### Additional context
Capability epic under #68227 covering E1-E6.
Contributor guide
Research direction
Start with capability epic #68227 and review its E1-E6 scope for Microsoft.AspNetCore.Components.Media. Identify how standalone and rich-node media integration should cover accessible metadata, downloads, sizing, loading, failure, and image affordances; done means the agreed capability scope is implemented and validated.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100