Skip to content

Conversation

@MackinnonBuck
Copy link
Member

Description

The IBrowserFile.ContentType field was not being correctly populated by the JS implementation for the InputFile component. This was caused by a change from the InputFile API review, which was applied in the C# implementation but not the JS implementation. This PR fixes that issue and adds tests verifying that all fields in IBrowserFile are correctly populated.

Customer Impact

Customers will now be able to use the IBrowserFile.ContentType field.

Regression?

No.

Risk

Virtually no risk. This PR is a simple variable rename with updated tests and test components.

Addresses #25679

@ghost ghost added the area-blazor Includes: Blazor, Razor Components label Sep 8, 2020
@pranavkm pranavkm added this to the 5.0.0-rc2 milestone Sep 8, 2020
@mkArtakMSFT mkArtakMSFT added Servicing-approved Shiproom has approved the issue Servicing-consider Shiproom approval is required for the issue and removed Servicing-approved Shiproom has approved the issue labels Sep 9, 2020
@ghost
Copy link

ghost commented Sep 9, 2020

Hello human! Please make sure you've included the Shiproom Template in a comment or (preferably) the PR description. Also, make sure this PR is not marked as a draft and is ready-to-merge.

@mkArtakMSFT
Copy link
Contributor

@Pilchie can we get this in for RC2?

@Pilchie Pilchie added Servicing-approved Shiproom has approved the issue and removed Servicing-consider Shiproom approval is required for the issue labels Sep 9, 2020
@Pilchie
Copy link
Member

Pilchie commented Sep 9, 2020

Approved for .NET 5 RC2.

@mkArtakMSFT mkArtakMSFT merged commit 43ef580 into release/5.0-rc2 Sep 9, 2020
@mkArtakMSFT mkArtakMSFT deleted the t-mabuc/input-file-content-type-fix branch September 9, 2020 20:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area-blazor Includes: Blazor, Razor Components Servicing-approved Shiproom has approved the issue

Projects

None yet

Development

Successfully merging this pull request may close these issues.

7 participants