Display warning message in console for unclosed tags
Reported by
stasvare...@gmail.com,
Nov 25
|
||||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/70.0.3538.102 Safari/537.36 Steps to reproduce the problem: If there is a tag that requires a closing tag Developer Tools should display a warning message with a link to that tag. It should also say that unclosed tags can lead to incorrect resulting markup. What is the expected behavior? What went wrong? Right now there is no way to tell that you have unclosed tags and you even might not know that you forgot to close them somewhere, because html engine does that for you. This could eliminate this problem once and for all. Did this work before? No Chrome version: 70.0.3538.102 Channel: n/a OS Version: 10.0 Flash Version:
,
Nov 26
,
Nov 26
Thanks for filing the issue! @Reporter: Could you please share a sample test file satisfying the conditions mentioned in C#0, which helps us to triage this further in a better way.
,
Nov 26
,
Nov 26
Thank you for providing more feedback. Adding the requester to the cc list. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Nov 29
stasvarenkin@ Thanks for the update. Able to reproduce this issue on Mac OS 10.13.6,Windows 10 and Ubuntu 17.10 on the latest Stable 70.0.3538.110 and latest Canary 72.0.3625.0 as per comment #4. Couldn't observe any error in Devtools -> Console when a file with unclosed tag is opened. This is a Non-Regression issue as this behavior is observed from M-60 chrome builds. Hence marking this as Untriaged for further updates from Dev. Thanks..
,
Dec 4
,
Dec 12
,
Dec 12
In the merged report, users would like to see warnings for non-standard tags that are not defined in customElements.define. Maybe a new type of live-audit would be appropriate for these cases. |
||||||
►
Sign in to add a comment |
||||||
Comment 1 by stasvare...@gmail.com
, Nov 25