Thread: Buglet?
View Single Post
Old 10-06-2020, 07:02 PM   #9
Tex2002ans
Wizard
Tex2002ans ought to be getting tired of karma fortunes by now.Tex2002ans ought to be getting tired of karma fortunes by now.Tex2002ans ought to be getting tired of karma fortunes by now.Tex2002ans ought to be getting tired of karma fortunes by now.Tex2002ans ought to be getting tired of karma fortunes by now.Tex2002ans ought to be getting tired of karma fortunes by now.Tex2002ans ought to be getting tired of karma fortunes by now.Tex2002ans ought to be getting tired of karma fortunes by now.Tex2002ans ought to be getting tired of karma fortunes by now.Tex2002ans ought to be getting tired of karma fortunes by now.Tex2002ans ought to be getting tired of karma fortunes by now.
 
Posts: 2,306
Karma: 13057279
Join Date: Jul 2012
Device: Kobo Forma, Nook
If you test it in W3C's Validation Service:

https://validator.w3.org/#validate_by_input

And give it XHTML with a "</p>>":

Code:
<?xml version="1.0" encoding="utf-8"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1//EN"
  "http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd">

<html xmlns="http://www.w3.org/1999/xhtml">
<head>
  <title></title>
</head>

<body>
  <p>Test</p>
  <p>And here's an error.</p>>
</body>
</html>
you get a "character data is not allowed here" error.

If you feed it similar in HTML:

Code:
<!DOCTYPE html>
<html>
<head>
  <title></title>
</head>

<body>
  <p>Test</p>
  <p>And here's an error.</p>>
</body>
no such error. It thinks it's fine...

If you do "<<p>" instead, both the XHTML1.1 + HTML5 checkers ping it.

Must be something obscure/weird in the HTML spec. Reminds me when I found that bug with the accidental <p">, and KevinH tracked it down. Turns out such a thing IS valid in HTML... but extremely poor practice.

Last edited by Tex2002ans; 10-06-2020 at 07:06 PM.
Tex2002ans is offline   Reply With Quote