You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 14, 2018. It is now read-only.
Functional tests are failing because await output.GetChildContentAsync(encoder) no longer changes the HTML encoder used when rendering the child content.
See Microsoft.AspNetCore.Mvc.FunctionalTests.TagHelpersTest.EncodersPages_ReturnExpectedContent(...) tests. Only the test using the default encoder works as expected.
The text was updated successfully, but these errors were encountered:
Also seeing failures in Microsoft.AspNetCore.Mvc.Razor.Host.Test and Microsoft.AspNetCore.Mvc.Razor.Test which may be related. Unfortunately, failing tests in Microsoft.AspNetCore.Mvc.Razor.Host.Test look like problems with generated class names and chosen TModel replacements. So, this issue may represent a cluster of recent Razor-related issues in MVC.
dougbu
changed the title
await output.GetChildContentAsync(encoder) no longer working
MVC Razor tests failing since the 10th
Feb 12, 2017
Functional tests are failing because
await output.GetChildContentAsync(encoder)
no longer changes the HTML encoder used when rendering the child content.See
Microsoft.AspNetCore.Mvc.FunctionalTests.TagHelpersTest.EncodersPages_ReturnExpectedContent(...)
tests. Only the test using the default encoder works as expected.The text was updated successfully, but these errors were encountered: