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 was archived by the owner on Apr 11, 2020. It is now read-only.
We have had a few issues filed around the .cshtml editor accepting non-void HTML elements without a separate end tag e.g. <select /> versus <select></select> (see aspnet/Mvc#4058) or <textarea/> versus <textarea></textarea> (see aspnet/Mvc#3964). The most common case is that an MVC tag helper targeting the element does not generate working HTML.
Anything we can do better to show .cshtml authors what they're writing is invalid would improve the user experience.
The text was updated successfully, but these errors were encountered:
If this issue is still a problem with the RTW release of Visual Studio 2017, please report a new issue using the Report a Problem tool. While you can still use .NET Core and ASP.NET Preview tools with Visual Studio 2015, Visual Studio 2017 is now the officially supported tool for developing .NET Core and ASP.NET Core projects.
By using the Report a Problem tool (available in both VS 2017 and VS 2015), you can collect detailed information about the problem, and send it to Microsoft with just a few button clicks. See Visual Studio's Talk to Us page for more details.
Please use the discussion topic here for feedback and questions on the deprecation of this issue tracker. Thanks!
We have had a few issues filed around the
.cshtml
editor accepting non-void HTML elements without a separate end tag e.g.<select />
versus<select></select>
(see aspnet/Mvc#4058) or<textarea/>
versus<textarea></textarea>
(see aspnet/Mvc#3964). The most common case is that an MVC tag helper targeting the element does not generate working HTML.Anything we can do better to show .cshtml authors what they're writing is invalid would improve the user experience.
The text was updated successfully, but these errors were encountered: