aspnet / Tooling

Issue tracker and info on Visual Studio tooling for ASP.NET
Other
256 stars 124 forks source link

Show warning when non-void element has an end tag #398

Open dougbu opened 8 years ago

dougbu commented 8 years ago

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.

barrytang commented 8 years ago

Tracked by TFS#189952 internally.

webtools-bot commented 7 years ago

The GitHub Issue Tracker for the aspnet/Tooling repo is being deprecated in favor of Visual Studio's Report a Problem tool.

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!