dotnet / dotnet/aspnetcore

Components.AI attachments, media, and voice

Open
#68,375 0 comments 0 reactions 0 assignees View on GitHub
area-blazor feature-blazor-builtin-components
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.

The built-in UI has incomplete attachment validation and transfer behavior, hand-rolled media rendering, no inline rich media, and no reusable voice-input capability.

### Describe the solution you'd like

Track three independently deliverable capability groups:

- Attachment validation, state, acquisition, transfer, progress, and cancellation.
- Standalone and inline media rendering through `Microsoft.AspNetCore.Components.Media`.
- A minimal JS interop module and reusable microphone input part.

This is a workstream under #68227. Capability groups and implementation tasks are represented as native sub-issues.

### Additional context

Covers A1, C4, D1-D8, and E1-E6 from #68227.

Contributor guide

Open the contributing guide

Research direction

Start with the parent workstream in #68227 and review the native sub-issues for the attachment, media, and voice capability groups. Use those sub-issues to identify the specific entry points and tests for an independently deliverable task. Done means the selected capability group or implementation task is completed and its stated validation, rendering, transfer, or voice behavior works as specified.

Written by the indexing model from the issue text.

Assessment

Tech stack
csharp, javascript
Domain
frontend, web-dev
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.