Opened 3 years ago
Closed 3 years ago
#54625 closed defect (bug) (reported-upstream)
Comments markup differs in trunk from the markup provided with the Gutenberg plugin active
Reported by: | kjellr | Owned by: | |
---|---|---|---|
Milestone: | Priority: | normal | |
Severity: | normal | Version: | 5.9 |
Component: | Editor | Keywords: | |
Focuses: | Cc: |
Description
Change History (7)
This ticket was mentioned in Slack in #core by kjell. View the logs.
3 years ago
This ticket was mentioned in Slack in #core by hellofromtonya. View the logs.
3 years ago
#4
@
3 years ago
Hmm, interesting. presumably it would make sense to opt into the markup as well. But if we do that, we'll also need to push some style updates in order to ensure that the block is properly rendered. The current Gutenberg appearance (with smaller meta font sizes, non-bold author name, and a post meta that doesn't slide off the screen) should be the target.
#5
@
3 years ago
Opened an issue in Gutenberg to add the comment-form
and comment-list
to the html5
theme supports https://github.com/WordPress/gutenberg/issues/37464.
@kjellr is there additional work that needs to be done in TT2? Should an issue be opened in the TT2 repo?
It looks like this came as a result of #54597 making it so that in Core we opt in to HTML5 markup for
comment-form
,comment-list
,style
andscript
:https://github.com/WordPress/wordpress-develop/blob/trunk/src/wp-includes/theme.php#L4179
In Gutenberg we only opt in to HTML5 markup for
style
andscript
:https://github.com/WordPress/gutenberg/blob/7762302a2aacd1da09d7c848ce009598aca21ef9/lib/compat/wordpress-5.9/default-theme-supports.php#L12-L18
I can make it so that the behaviours in Core and Gutenberg match, but which is correct, @kjellr? We should aim to use HTML5 markup, no?