Query Loop - Add accessibility markup at the end of the loop in all cases.

[cbravobernal]

What?

As the enhanced query loop is adding accessibility tags at the end of the markup. It was searching for a div tag.
The query loop can have also aside, section, a different tag than just a div. So, with this PR, the markup is added at the end of the query loop always.

Testing Instructions

1. Add a query loop with pagination, more than 3 posts, 3 posts per page in configuration. Disable force reload.
2. Set the query loop HTML element as a non default tag (section, aside, etc).
   3)At the frontend, check that

<div
	class="wp-block-query__enhanced-pagination-animation"
	data-wp-class--start-animation="selectors.core.query.startAnimation"
	data-wp-class--finish-animation="selectors.core.query.finishAnimation"
></div>

is at the end of the query loop markup.

Testing Instructions for Keyboard

Screenshots or screencast

Before:

After:

[github-actions]

Flaky tests detected in ab2d4f5.
Some tests passed with failed attempts. The failures may not be related to this commit but are still reported for visibility. See the documentation for more information.

🔍 Workflow run URL: https://github.com/WordPress/gutenberg/actions/runs/6776643938
📝 Reported issues:

• [Flaky Test] should select with shift + click #48390 in /test/e2e/specs/editor/various/multi-block-selection.spec.js

[luisherranz]

Looks good to me, thanks Carlos. I just have one question below 🙂

[github-actions]

This pull request has changed or added PHP files. Please confirm whether these changes need to be synced to WordPress Core, and therefore featured in the next release of WordPress.

If so, it is recommended to create a new Trac ticket and submit a pull request to the WordPress Core Github repository soon after this pull request is merged.

If you're unsure, you can always ask for help in the #core-editor channel in WordPress Slack.

Thank you! ❤️

View changed files

❔ phpunit/blocks/render-query-test.php

[mikachan]

I just cherry-picked this PR to the 6.4-next-point-release branch to get it included in the next release: be23264