Das sieht nach einem “Race Condition” aus, also versuche ich etwas anderes, um zu erkennen, wann der > Breadcrumb-Trennzeichen angezeigt oder ausgeblendet werden soll.
main ← fix-breadcrumb-separator-race
opened 10:38AM - 20 Apr 26 UTC
The breadcrumb `>` separator was rendered on every item and hidden on the last o… ne via a `li:last-child` CSS rule. That worked for static breadcrumbs, but `DeferredTrackedSet.add()` defers item registration through `next()`. When navigating into a child route (e.g. `/admin/backups/logs`), the new `DBreadcrumbsItem` mounts and renders before its `add()` flushes — leaving the previously-last `<li>` as the DOM's actual `:last-child` for one tick, so its `>` disappears until the next re-render brings everything back into sync. On the backups page, frequent MessageBus updates during a running backup made that window visible: the arrow would intermittently drop until the user navigated out and back in.
Bind separator visibility to the tracked-set index instead: `DBreadcrumbsContainer` passes `@isLast` to each item, and `DBreadcrumbsItem` only renders the separator when `@isLast` is false. The CSS rule is gone. Separator presence now tracks the authoritative Set state rather than the DOM's transient structure, closing the stale-last-child window.
https://meta.discourse.org/t/400730
2 „Gefällt mir“