F12 console messages lack open bracket of element names but include close bracket

Confirmed Issue #13591674 • Assigned to edgedevtoolstri@microsoft.com

Details

Author
Richard S.
Created
Sep 5, 2017
Privacy
This issue is public.
Found in
  • Microsoft Edge
Found in build #
16.16281
Reports
Reported by 1 person

Sign in to watch or report this issue.

Steps to reproduce

The following are examples from the F12 console on 16281. The flaw is that the open bracket of the element name is not included but the close bracket is.

HTML1511: Unexpected head-level element encountered outside of "head>".
Default (26,8)

HTML1514: Extra “body>” tag found. Only one “body>” tag should exist per document.
Default (391,13)

HTML1521: Unexpected “/body>” or end of file. All open elements should be closed before the end of the document.
Default (391,308)

Attachments

0 attachments

    Comments and activity

    • Microsoft Edge Team

      Changed Assigned To to “James M.”

    • Hello,

      Thank you for providing this information about the issue. Unfortunately, we are unable to reproduce this problem in Edge with the information at hand. Please update this case when you can provide more details, such as a reduce sample code or a sample webpage.

      Best Wishes,
      The MS Edge Team

    • Visit https://outlook.live.com/mail/. On 15063 the console message is

      HTML1527: DOCTYPE expected. Consider adding a valid HTML5 doctype: "".
      mail (1,1)

      On 16281 the console message is

      HTML1527: DOCTYPE expected. Consider adding a valid HTML5 doctype: "!DOCTYPE html>".

    • This web site inappropriately removed the !DOCTYPE element. Here it is again with angle brackets replaced by braces. Hopefully this will not be inappropriately mangled again.

      HTML1527: DOCTYPE expected. Consider adding a valid HTML5 doctype: "{!DOCTYPE html}".
      mail (1,1)

    • Microsoft Edge Team

      Changed Assigned To to “edgedevtoolstri@microsoft.com”

      Changed Status to “Confirmed”

    You need to sign in to your Microsoft account to add a comment.

    Sign in