The one result I'm seeing is what I'm now referring to as a vomit bug.
Book nowModern Universal React with Next.js
Stop worrying about configuration, and complex codebases: Next.js makes SSR with React easy. Book your masterclass today.
- Vomit bug
- When the browser's parser rearranges the DOM completely differently to the markup, resulting in content being placed outside its original container.
For example, due to a bug in Firefox 3.5.2 (and perhaps before) the following markup is subject to the vomit bug:
<a href="#"> <section> <p>p nested in a section wrapped in a link</p> </section> </a>
The resulting DOM is as such:
<a href="#"> <section></section> </a> <p> <a href="#">p nested in a section wrapped in a link</a> </p> <a href="#"></a>
This is a particular bug in Firefox that triggers when it parses a
section element nested inside an
a element that causes all currently open element to close, and the contents of the
section element has been "corrected" by the browser and the DOM rearranged.
You can see a live example here: http://jsbin.com/upiza
What other vomit bugs have you found?