You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
E.g. on previous PR consistently added them #16952 - but since the last 3 years (even back then it was outdated) it's become completely unused and should be removed.
Screenshots, screen recording, code snippet
If possible, please provide a screenshot, a screen recording or a code snippet which demonstrates the bug.
Technical info
Used versions
Yoast SEO version: 23.9
The text was updated successfully, but these errors were encountered:
This issue is a duplicate of the issue #2223, which got marked as closed with no plan to change this as it was not causing any problems or breaking anything with the meta tag being read by search engines. However, I asked our development team to check whether this change is required or not.
Thanks. The referenced issue is almost 10 years old and things have changed since then, therefore I think it's valid to bring this up again. Especially if you look at the recent comments on that issue e.g. #2223 (comment)
Please give us a description of what happened
To Reproduce
Step-by-step reproduction instructions
Expected results
>
Actual results
Void elements contain outdated XHTML
/>
which is not valid HTML (but silently ignored)https://developer.mozilla.org/en-US/docs/Glossary/Void_element
WordPress never serves a page with content-type application/xhtml+xml, therefore the XHTML compatibility is pointless.
WP core is currently also undergoing some changes to fix it in core https://core.trac.wordpress.org/ticket/59883
E.g. on previous PR consistently added them #16952 - but since the last 3 years (even back then it was outdated) it's become completely unused and should be removed.
Screenshots, screen recording, code snippet
If possible, please provide a screenshot, a screen recording or a code snippet which demonstrates the bug.
Technical info
Used versions
The text was updated successfully, but these errors were encountered: