#58915 closed defect (bug) (fixed)
Twenty Thirteen and Twenty Sixteen: change display for the summary element in Details blocks
| Reported by: |
|
Owned by: |
|
|---|---|---|---|
| Milestone: | 6.4 | Priority: | normal |
| Severity: | normal | Version: | 6.3 |
| Component: | Bundled Theme | Keywords: | has-patch has-test-info has-screenshots commit |
| Focuses: | css | Cc: |
Description
Both Twenty Thirteen and Twenty Sixteen set the summary element to display: block in the Reset/Normalize section of their stylesheets. When using the Details block, this removes or hides the toggle triangle native to the browser.
Other default themes:
- Twenty Seventeen, Twenty Nineteen and Twenty Twenty-One set the
summarytolist-itemdisplay. - The other eight themes rely on the browser's native
displaystyling.
Attachments (5)
Change History (15)
#1
@
2 years ago
- Keywords has-patch added
Removing summary from the normalized styles would be easier, but some people may have created a custom toggle marker that works with the block display for a details element (not using the new WordPress block).
#2
@
2 years ago
- Milestone changed from Awaiting Review to 6.3.1
I have tested patch 58915.patch manually on macOS in various browsers, and it works well for me.
#3
@
2 years ago
Test Report
Patch tested: https://core.trac.wordpress.org/attachment/ticket/58915/58915.patch
Env
- WordPress - 6.4-alpha-20230819.191300
- Web Server: Nginx
- Chrome Version - 115
- OS - macOS
- Theme: Twenty-Thirteen, Twenty-Sixteen
- PHP - 7.4.0
- Active Plugin - None
Test result ✅
The purpose of this testing was to assess the behavior of the arrow icon within the details block across two default WordPress themes: Twenty-Sixteen and Twenty-Thirteen. The testing aimed to verify if the arrow icon correctly appears as intended in revealing and concealing the additional content within the details block.
The toggle arrow icon works fine after the patch in the editor as well as the front end.
After the patch-
Twenty Thirteen:
Twenty Sixteen:
#5
@
2 years ago
- Milestone changed from 6.3.1 to 6.3.2
WP 6.3.1 is going to be released in the next few days, so let's move this ticket to 6.3.2 to give it more time to be committed and backported.
#7
@
2 years ago
@poena I'm checking on some tickets in the 6.4 milestone to make sure we're ready for RC1 in ~2 weeks. It looks like this ticket has passing test reports. Do you think this is ready for a commit? Would you like to take ownership and usher it through? :)


Details block in the editor, with Twenty Thirteen