Malformed HTML parsed differently from browsers #512

Activity

1. demurgos

   changed the title [-]Malformed HTML parsed differently from Firefox and Chrome[/-] [+]Malformed HTML parsed differently from browsers[/+] on Oct 1, 2023
2. demurgos commented on Oct 1, 2023

   

   demurgos

   on Oct 1, 2023

   Last edited by demurgos

   Author

   More actions

   Running the arena example, I actually get a result close to real browsers.

   I added Debug to html5ever/examples/arena:

   impl<'arena> std::fmt::Debug for Node<'arena> {
       fn fmt(&self, f: &mut Formatter<'_>) -> std::fmt::Result {
           f.debug_struct("Node")
               .field("data", &self.data)
               .field("first_child", &self.first_child)
               .field("next_sibling", &self.next_sibling)
               .finish()
       }
   }
   

   And then executed:

   $ cat ./malformed.html
   <html><body><div><a hr</div><div><div></div>
   <div><a href="/">bar</a></div></div></body></html>
   $ cargo run --example arena < ./malformed.html
   

   This produced a tree corresponding to:

   <document>
     <html>
       <head></head>
       <body>
         <div>
           <a hr<="" div=""></a>
           <div>
             <a hr<="" div="">
               <div></div>
               "\n"
             </a>
             <div>
               <a hr<="" div=""></a>
               <a href="/">bar</a>
             </div>
           </div>
           "\n"
         </div>
       </body>
     </html>
   </document>
   

   The difference with real browsers is that:

   • there is a <div> inside the second anchor, while it's empty inside browsers.
   • the broken anchors have two attributes instead of three

   Regarding the other differences, they may be caused by my TreeSink, I'm using html5ever through scraper so I'll check there too.