RESOLVED DUPLICATE of bug 304208304241
<details> marker uses emoji in closed state but non-emoji in open state on iOS 26
https://bugs.webkit.org/show_bug.cgi?id=304241
Summary <details> marker uses emoji in closed state but non-emoji in open state on iO...
Joel Kanerva
Reported 2025-12-16 01:57:05 PST
Created attachment 477742 [details] Screenshots showing how arrows render On iOS 26.1, the default disclosure marker for the HTML <details> element renders inconsistently between the closed and open states. When the <details> element is closed, the marker inside the <summary> element appears as an emoji-style right-pointing triangle arrow (▶️). When the <details> element is opened, the marker changes to a down-pointing triangle that is rendered as a non-emoji glyph. The result is a visual mismatch between the two states. This regression was not observed on earlier iOS versions (for example, iOS 18), where both the closed and open markers were rendered as non-emoji glyphs.​ Steps to Reproduce Use an iOS 26 device (Safari or any WebKit-based web view). Open a simple HTML page containing the following markup: xml <details> <summary>Income by postal code</summary> <p>Example content.</p> </details> Example websites with this bug: - https://web.dev/learn/html/details - https://www.w3schools.com/tags/tryit.asp?filename=tryhtml5_details_css Other people reporting issue: - https://developer.apple.com/forums/thread/807094 Actual Results Closed state: The disclosure marker is a right-pointing emoji arrow (▶️). Open state: The disclosure marker is a non-emoji down-pointing triangle glyph. The change in style between emoji and non-emoji markers looks visually inconsistent and unpolished. Expected Results The disclosure markers in both closed and open states should use a consistent non-emoji glyph (for example, small black triangles like ▸ and ▾), matching the behavior of previous iOS versions and other platforms.​
Attachments
Screenshots showing how arrows render (76.72 KB, image/jpeg)
2025-12-16 01:57 PST, Joel Kanerva
no flags
Alexey Proskuryakov
Comment 1 2025-12-16 10:19:25 PST
Thank you for the report! Looks like this is being fixed right now. *** This bug has been marked as a duplicate of bug 304208 ***
Note You need to log in before you can comment on or make changes to this bug.