Bug 249594

Summary: HTML details marker does not update when CSS display: contents is applied
Product: WebKit Reporter: Šime Vidas <sime.vidas>
Component: Layout and RenderingAssignee: Nobody <webkit-unassigned>
Status: RESOLVED DUPLICATE    
Severity: Normal CC: bfulgham, darin.senneff, karlcow, ntim, simon.fraser, webkit-bug-importer, zalan
Priority: P2 Keywords: BrowserCompat, InRadar
Version: Safari 16   
Hardware: Mac (Intel)   
OS: macOS 13   
Bug Depends on:    
Bug Blocks: 252223    

Šime Vidas
Reported 2022-12-19 10:41:32 PST
Steps to reproduce: 1. Open https://jsbin.com/yaxizom/edit?html,css,output 2. Click “Details” What happened: The triangle marker ▶︎ does not change. What should have happened: The marker should have turned down (▼). It does in Chrome and Firefox.
Attachments
Šime Vidas
Comment 1 2022-12-19 10:53:33 PST
I’ve checked how VoiceOver is affected. The collapsed state is announced, but the expanded state isn’t.
Karl Dubost
Comment 2 2022-12-19 18:08:46 PST
In the section https://drafts.csswg.org/css-display/#unbox > Appendix B: Effects of display: contents on Unusual Elements > Some elements aren’t rendered purely by CSS box concepts; > for example, replaced elements (such as img), many form > controls (such as input), and SVG elements. > > This appendix defines how they interact with display: contents. > > HTML Elements > > … cut for brevity … > > button > details > fieldset > These elements don’t have any special behavior; display: contents > simply removes their principal box, and their contents render as normal. > https://searchfox.org/wubkat/rev/05f693e31a84e598a51d00bf3505f1e10049bbc5/Source/WebCore/html/HTMLSummaryElement.cpp
Radar WebKit Bug Importer
Comment 3 2022-12-19 18:08:57 PST
Darin Senneff
Comment 5 2023-11-08 09:28:45 PST
Confirmed that this is still present in Safari 17.1 on MacOS. Adding the CSS "display: contents;" on the 'details' element causes the disclosure triangle to remain pointing sideways in both open and expanded states.
Tim Nguyen (:ntim)
Comment 6 2024-11-23 11:33:33 PST
Fixed by bug 157323. *** This bug has been marked as a duplicate of bug 157323 ***
Note You need to log in before you can comment on or make changes to this bug.