Welcome to WebmasterWorld Guest from 34.204.189.171

Forum Moderators: open

"HTML1521 unexpected /body or end of file" warning in Edge

     
10:05 pm on Aug 28, 2019 (gmt 0)

Junior Member

10+ Year Member

joined:July 14, 2009
posts:139
votes: 0


Hello!
I get "HTML1521 unexpected /body or end of file" warning in Edge browser. Is it something to worry about or just disregard as non-issue?
10:56 pm on Aug 28, 2019 (gmt 0)

Administrator from US 

WebmasterWorld Administrator not2easy is a WebmasterWorld Top Contributor of All Time 10+ Year Member Top Contributors Of The Month

joined:Dec 27, 2006
posts:4510
votes: 348


Where are you seeing this? Is the browser just freely telling you "HTML1521 unexpected /body or end of file" all by itself?
11:06 pm on Aug 28, 2019 (gmt 0)

Senior Member from US 

WebmasterWorld Senior Member lucy24 is a WebmasterWorld Top Contributor of All Time 5+ Year Member Top Contributors Of The Month

joined:Apr 9, 2011
posts:15874
votes: 872


not2easy, see also the adjoining thread “unmatched end tag” [webmasterworld.com].

abrodski, you have not yet said--in this thread or the other one--whether these messages are popping up on your own pages or on random other pages you’re browsing. If it concerns other people’s pages, the question may get a more useful answer in the Edge and MSIE subforum [webmasterworld.com]. If it is about your own pages, use a validator for more information.
11:55 pm on Aug 28, 2019 (gmt 0)

Administrator from US 

WebmasterWorld Administrator not2easy is a WebmasterWorld Top Contributor of All Time 10+ Year Member Top Contributors Of The Month

joined:Dec 27, 2006
posts:4510
votes: 348


I'll guess that the page(s) in question are your own. To determine whether there are errors, you can use the HTML Validator [validator.w3.org] to check the HTML and tell you if there are items you can fix. Generally they offer a report that lists any errors and how to fix them.
12:38 am on Aug 29, 2019 (gmt 0)

Junior Member

10+ Year Member

joined:July 14, 2009
posts:139
votes: 0


not2easy,
Browsers can't do stuff by themselves yet. Maybe except for annoying push-messages :-)
I myself did press F12 buttom to call the Dev Tools of the FF. THERE in "Console" section I'd seen what I told you I had.
12:40 am on Aug 29, 2019 (gmt 0)

Junior Member

10+ Year Member

joined:July 14, 2009
posts:139
votes: 0


lucy24,
My question here and there is very simple, actually. Not how to correct those issues, but do I have to. If those issues aren't critical for my site's well-being and its proper functioning, then I won't bother. Since I'm not a coder it's not so easy for me just to fix them.
1:00 am on Aug 29, 2019 (gmt 0)

Senior Member

WebmasterWorld Senior Member Top Contributors Of The Month

joined:Apr 1, 2016
posts:2711
votes: 822


Not how to correct those issues, but do I have to.

There is really know way for anyone to answer this question without knowing the specifics of the page. The browser is most likely rendering the page despite the error and everything is fine. But there may be some unexpected impacts that you are not seeing. Ideally one would want to correct the error.

Given that you are experiencing both errors together, it would suggest to me that there is an issue with the closing body tag. Possibly appearing twice in the document. I would run the page through the W3 validator, find the problem. Then it should be easily fixed.
4:37 am on Aug 29, 2019 (gmt 0)

Senior Member from US 

WebmasterWorld Senior Member tangor is a WebmasterWorld Top Contributor of All Time 10+ Year Member Top Contributors Of The Month

joined:Nov 29, 2005
posts:10458
votes: 1091


Looking up these errors (also the other 1509 post) on the MS website/forums ... these are ordinary errors for webpage failure to meet strict html tags, going back to IE9 through the latest iteration of IE and also found in Edge as well. MOST appear to be a result of using <p> incorrectly, but not always.

YMMV
4:08 am on Aug 30, 2019 (gmt 0)

Junior Member

10+ Year Member

joined:July 14, 2009
posts:139
votes: 0


Thank you all for your input! So, basically, translating it from English into English, if I'm not a coder and my site renders fine, I can just leave it as is.