Why. Owner: "i never really liked the 'X new - refresh'. can we not just stream??" The forge already pushes live updates to regions of a page; a bar asking the reader to refresh is the page declining to do its job.
What.
Lists and feeds that show "N new — refresh" instead receive new rows as they happen, over the live channel the pages already use (no new dependency).
The reader's place is never moved: if they are at the top, new rows slide in; if they have scrolled or are reading or typing, new rows are added above without shifting what is on screen, and a small quiet marker ("3 above") lets them jump up when they choose. Nothing they are interacting with is replaced under them (data-live-hold semantics).
Order stays stable; a row that changes updates in place rather than jumping. When the connection drops the page says so in a word and catches up when it returns, with no refresh.
A burst (more than a handful in a second) is batched so the page does not thrash.
Find every place the refresh bar appears and convert each; remove the bar component when none use it.
Acceptance. Browser tests: a new item appears at the top within a second with no click; with the reader scrolled, content does not shift and the marker appears; a dropped connection recovers without a reload. No page renders the words "new — refresh".
Why. Owner: "i never really liked the 'X new - refresh'. can we not just stream??" The forge already pushes live updates to regions of a page; a bar asking the reader to refresh is the page declining to do its job.
What.
data-live-holdsemantics).Acceptance. Browser tests: a new item appears at the top within a second with no click; with the reader scrolled, content does not shift and the marker appears; a dropped connection recovers without a reload. No page renders the words "new — refresh".