Notice (2018-05-24): bugzilla.xamarin.com is now in
Please join us on
Visual Studio Developer Community and in the
Mono organizations on
GitHub to continue tracking issues. Bugzilla will remain
available for reference in read-only mode. We will continue to work
on open Bugzilla bugs, copy them to the new locations
as needed for follow-up, and add the new items under Related
Our sincere thanks to everyone who has contributed on this bug
tracker over the years. Thanks also for your understanding as we
make these adjustments and improvements for the future.
Please create a new report for Bug 11613 on
Developer Community or GitHub if you have new
information to add and do not yet see a matching new report.
If the latest results still closely match this report, you can use the
In special cases on GitHub you might also want the comments:
GitHub Markdown with public comments
I'm using monodevelop build from git under Linux, on MVC application in razor page I'm getting warnings:
Parser Waring: Tag '' implicitly closed by tag '' when in I have self closed tag in container tag
<input type="text" />
Parser Waring: Tag 'td' implicitly closed by tag 'input'
Parser Waring: Tag 'div' implicitly closed by tag 'br'
Here I'm getting several warnings:
Line 1: Parser Waring: Tag 'td' implicitly closed by tag 'div'
Line 2: Parser Waring: Tag 'div' implicitly closed by tag 'ul'
Line 4: Parser Waring: Tag 'li' implicitly closed by tag 'input'
Line 7: Parser Waring: Tag 'li' implicitly closed by tag 'input'
I don't think that there should be a warning ?
A in this situation I'm getting same warning:
Line 1: Parser Waring: Tag 'td' implicitly closed by tag 'select'
I'm having this issue in MonoDevelop 4.1.11 (build 10), but it's being treated as an error instead of a warning, can anyone tell me how to change this behavior?
This is a real nasty bug and its severely impeding development.
I have upgraded from the old MonoDevelop to Xamarin and this isn't allowing me to send out site updates.
It shows up as an error not a warning, which makes it suck even more.
Im my case its a <br/> inside a <p> that causes the issue.
Anyone fancy trying to improve the auto-closing logic? :)
Any cared to fix this yet?
Pls fix this bug as soon as possible..
+1 - this is also killing my builds by HTML 5 that is valid.
Did anybody find a solution to this? I ran into the same problem ;(