| 19:47 | <MikeSmith> | it’s not possible to use a custom element in the head, right? |
| 19:53 | <Domenic> | MikeSmith: not via the parser, but you could always insert it with the DOM APIs |
| 20:05 | <MikeSmith> | Domenic: ah OK yeah — thanks |
| 20:05 | <MikeSmith> | context is https://github.com/w3c/markup-validator/issues/49 |
| 20:16 | <Domenic> | MikeSmith: yeah so I think that person is in the wrong and the validator is right. What's actually happening on their page is their custom element is inserting an implicit </head> before itself and that's probably not what they intended |
| 20:16 | <Domenic> | You can test this with live dom viewer |
| 20:17 | <MikeSmith> | right |
| 20:17 | <Domenic> | Also just from a validity perspective <head>'s content model is metadata elements only which does not include custom ones |
| 20:17 | <MikeSmith> | oh good point |
| 20:18 | <MikeSmith> | but anyway yeah, in other words, what the HTML parser in the validator is doing is he same thing that browser parsers are doing; the OP just doesn’t realize that browsers are doing it too |
| 20:18 | <MikeSmith> | will comment there |