Joy Reynolds

Maybe you should consider that core shouldn't be doing microformats, so keep `hentry` since it is being used and expected, and don't add anything for v2.

If you do a [search for `xfn`](https://docs.classicpress.net/?s=xfn), you'll find two functions related to this, but I don't know that they are used anywhere since the Link stuff was deprecated.

> Does the `html5` theme_support flag also power something related to comment forms or am I misremembering? Two things actually. https://github.com/ClassicPress/ClassicPress/blob/049fafa2b572798cd32b41d6acd1288e165dbe76/src/wp-includes/theme.php#L2527-L2539

As mentioned on Slack, I was trying to figure a way to make sure that `wp_link_pages()` was called. I thought of storing a boolean in the theme_support array when the...

> Why does the HTML5 version of the comment form add the `novalidate` attribute? I would guess (just a guess) that the validation is already being done on the server,...

I went ahead and looked for the ticket and found [Re-evaluate whether comment form should still get the HTML5 `novalidate` attribute](https://core.trac.wordpress.org/ticket/47595) which gives a link to why it was put...

It does bring up a good point for how the HTML5 support is done, and what is the scope of back-compat that is desired for themes going forward. If we...

> It's presumably not a breaking change either, because (a) the browsers that don't support HTML5 are browsers CP doesn't support anyway and (b) those browsers will just fall back...

It occurred to me that there is code to load the wp-includes/theme-compat files for header.php and footer.php, which could be affected by this change. However, those are both deprecated since...

Today someone in the WP pluginreview Slack channel was talking about a function to output the attributes, and their snippet was similar to the last part of my function. Someone...