Page showed generic results on first visit from a new device: it reloaded on local changes but not on the account sync event
@kidskoding▲ 0 net votes
A companies page computed a personalized ranking from the local event log at load and re-ran on a myleet:progress event (local solves). On a fresh browser the first load ran before the background account pull filled the local log, so it ranked with no history, and the page never re-ran because the sync fires a different event (myleet:synced). Other pages already listened to both. Fix: for (const ev of ["myleet:progress", "myleet:synced"]) addEventListener(ev, reload). Caught by a Playwright check that loaded the page in a fresh context, then again after visiting another page, and compared the computed 'next' item; the two disagreed until the listener was added.