Remove hAtom from core

[joostdevalk]

We output hAtom in core and well, it's just not really needed anymore, so I'd like to get rid of it.

Here, amongst other places:

https://core.trac.wordpress.org/browser/tags/4.8.1/src/wp-includes/post-template.php?marks=505,506#L496

[SergeyBiryukov]

Introduced in [8641] as a part of sticky posts. No reasoning for hentry is mentioned in the ticket though: #7457.

[swissspidy]

See #32336 and #32326. The big problem is that many themes use hentry for styling.

[netweb]

Replying to swissspidy:

See #32336 and #32326. The big problem is that many themes use hentry for styling.

Also https://core.trac.wordpress.org/ticket/30783#comment:27 tl;dr: - hentry will *not* be removed from core

[grapplerulrich]

The big problem is that many themes use hentry for styling.

We can solve the by introducing a add_theme_support that allows themes to remove it automatically without needs all themes to add hacks like

<?php
function _s_body_classes( $classes ) {
        // Adds a class of hfeed to non-singular pages.
        if ( ! is_singular() ) {
                $classes[] = 'hfeed';
        }
        return $classes;
}
add_filter( 'body_class', '_s_body_classes' );

function _s_post_classes( $classes ) {
        if ( 'page' === get_post_type() ) {
                $classes = array_diff( $classes, array( 'hentry' ) );
        }
        return $classes;
}
add_filter( 'post_class', '_s_post_classes' );

Did not mean to remove the close keyword but I don't agree it should be closed.

[callumbw95]

Hi @grapplerulrich,

The proposal to use add_theme_support() to manage this change was a thoughtful approach to handling the significant backward compatibility issue, especially concerning themes that rely on the .hentry class for styling.

Given this ticket has been stalled for years without a consensus around this, I recommend we re-add the close tag for now. 😃