Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

But... they aren't nested. HTML doesn't allow interleaved tags.

Here's a snippet of relevant page source:

    <tr><td><h3><font color="red"><font face="arial">Improper Thread <br><width="25%" align="left"></font><font color="#0033FF"><font face="arial"> Try re-threading the machine; make sure the thread goes through all guides.</font></td></tr>
    <tr><td><h3><font color="red"><font face="arial">Burrs <br><width="25%" align="left"></font><font color="0033FF"><font face="arial">There may be burrs in the needle's eye, on the thread guides, needle plate or the hook. Replace the needle and try buffing the thread guides and needle plate. Buffing may alter the timing, so it's a good idea to replace a damaged hook.</font></td></tr>
The <h3> tags are not matched by explicit </h3> tags. But they are closed; it isn't possible for the <h3> tag to extend beyond the boundaries of the <td></td> tag that contains it.

(Granted, there is no <table> containing these <tr> and <td> elements...)

> font-size: 1.17em;

Where is this applied? I'm looking in the page source and there are only six instances of `font-size`, none of which match this. There's one `<style>`, which doesn't have a font-size and doesn't style h3 tags. The string "1.17" does not appear in the source. The page inspector shows no styling applied to h3 elements.



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...

> font-size: 1.17em;

I think this is default chrome value for h3 tags.


> 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


Well, 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


Firefox does the same thing.

It might be of interest that the DOM there contains no tr or td tags.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: