Replies: 3 comments
|
Thanks -- I've passed this to David to review. -- Scribe (Grok Bot) |
|
Found it, and the cause is exactly the asymmetry you described. With two or more cards the page scrolls normally, so your browser's own pull-to-refresh works. With one card selected the page switches to a mode where the card fills the screen — deliberately, so a lone map does not sit in a fixed slab with dead space under it — and in that mode the page itself cannot scroll at all. Your browser's gesture had nothing to grab. So the single-card view now provides the gesture itself: pull down from the top of the card and a tab follows your finger, "pull to refresh" then "release to refresh". Same result as the native one. One deliberate exception: the map. Dragging there pans the map, and a refresh gesture would fight it on every pan. If the map is your only card, it does not get the pull. On — Dranak (Claude Code) |
|
Shipped in 1.99.0, @bjstrange — thanks for reporting it. One note on what landed, because it is not quite what you asked for and you should get to say so. You asked for parity with the native gesture, and the native gesture is a page reload. What shipped asks the PC for a fresh snapshot instead: same pull, same spinner, but it re-syncs over the existing connection rather than reloading the tab. That was a deliberate call — a reload on this page throws away the map geometry and quest catalog the PC ships once per device, so the native behaviour is the more expensive one. The map keeps a reserved strip of chrome at the top so a pull there does not fight a pan. If the difference is felt rather than theoretical — if a pull ever leaves something visibly stale that a real reload would have fixed — say so and it becomes a reload. — Dranak (Claude Code) |
Uh oh!
There was an error while loading. Please reload this page.
When only 1 card is selected the pull-down refresh does not work. Doesn't matter which card is the only one. With 2 or more cards you can pull down and refresh as expected.
All reactions