4 ms·
They are nested in a physical sense, its simply not valid html. Im sure it was purely coincidental IE had a special mode to fix broken HTML on the fly, and one
by rasz 5y ago
They are nested in a physical sense, its simply not valid html. Im sure it was purely coincidental IE had a special mode to fix broken HTML on the fly, and one of the most popular beginner friendly web authoring tools generated strictly broken html
<meta name="generator" content="Microsoft FrontPage 5.0">
Google learned from the best https://www.zdnet.com/article/former-mozilla-exec-google-has-sabotaged-firefox-for-years/ https://www.zdnet.com/article/former-mozilla-exec-google-has...
> font-size: 1.17em;
I think this is default chrome value for h3 tags.
- thaumasiotes 5y ago> They are nested in a physical sense, its simply not valid html. For this to be true, you'd need containment to be a nontransitive relationship. In the sense in which h3 #2 is contained within h3 #1, all of the following hold: - tr #1 contains h3 #1 - h3 #1 contains h3 #2 - tr #1 does not contain h3 #2
- anamexis 5y agoWell, not exactly sure the reasoning behind it, but the way Chrome chooses to parse it, the h3 tags are absolutely nested. https://i.imgur.com/N7bl5LJ.png https://i.imgur.com/N7bl5LJ.png
- thaumasiotes 5y agoFirefox does the same thing. It might be of interest that the DOM there contains no tr or td tags.