A reader report (credited to Kilian) flagged that the <details> element on one of our blog posts had lost its default ▶ disclosure icon, rendering it visually indistinguishable from an ordinary paragraph.

Tracing the Cause
Diagnosis was straightforward: opening the page in Firefox, inspecting the element in DevTools, and toggling properties until the marker reappeared. The culprit turned out to be an outdated copy of Normalize.css that had survived multiple site redesigns and was still applying a display override:
summary {
display: block; /* the problem */
}
With that rule in effect, Firefox drops the ▶ entirely:
Careful not to `display: block` your <summary> elements, lest lose the ▶ in Firefox. My old copy of Normalize.css had that in there. pic.twitter.com/06KHY892dT
— Chris Coyier (@chriscoyier) January 6, 2021
The fix landed upstream in 2016, when Jon Neal adjusted the rule in Normalize to use a different display value:
summary {
display: list-item;
}
How Browsers Differ
The discrepancy stems from user-agent styles. Chrome's UA stylesheet already declares <summary> as display: block, so overriding it with block changes nothing. Firefox, as far as can be determined, uses list-item instead. That explains why the current Normalize release sets the value to list-item.

Firefox DevTools also shows the ▶ being rendered via a ::marker pseudo-element. Once <summary> stops being a list-item, the ::marker vanishes — consistent with the specification:
The
::markerpseudo-element represents the automatically generated marker box of a list item.
Chrome, by contrast, appears to allow ::marker on block-level items; whether that is a bug is debatable. It is arguably a useful behavior — Šime Vidas has previously highlighted how handy it is to have ::marker apply to more than list items.
Safari is unaffected: the ▶ there appears to originate from shadow content rather than the marker mechanism shown in the other engines.

Takeaway
Normalize's approach of forcing list-item is a reasonable one, and leaving <summary>'s display untouched avoids the problem altogether. Anyone overriding display on <summary> should be aware that doing so removes the disclosure marker in Firefox.



