Notice when the same table is open twice #79

2026-09-01T18:35:51-06:00

jheaps commented

2026-09-01 18:35:51 -06:00

Opening the tool in a second tab — tapping the bookmark again rather than hunting for the tab you already had — silently throws away whatever the first one is doing. Stacked on #78.

Each tab holds its own copy in memory and each save writes the whole table, so the second one to act wins. Driven with two tabs on one profile:

tab A: deal, and Ann calls    stored -> bettingOpen true,  committed [0,1,2,2]
tab B: type a name in seat 5  stored -> bettingOpen false, committed [0,0,0,0]

The deal, the blinds and the call are gone, and neither tab said anything. That's the same silent shape as the save and load failures either side of this change.

The browser already tells us

A storage event fires in every other tab when the key changes, and never in the one that wrote — so our own saves can't trip it. A tab that sees its table move underneath it now says so, once, with the way out attached:

toast: This table is open in another tab. Whichever acts last wins. [Reload]

panel: This table is open in another tab, and both are writing to it — whichever acts last wins, so work done in the other one can vanish. Close one, then reload this tab to pick up the table as it stands.

Watched rather than merged, deliberately. Replacing the table under a dealer's hands in the middle of a hand would be its own hazard, and reloading is the only resolution that doesn't throw somebody's work away — so it's offered rather than taken.

Validation

6 tests (269 total): a write from elsewhere is noticed, another app's key and our own recovery key aren't our business, ten writes produce one warning, watching twice listens once, no listener isn't an error, and no window at all isn't an error.

Driven with two live tabs: both quiet at first, A deals and B warns with the reload offer, A stays quiet about its own writes, two more actions in A add no further toasts in B, and reloading B picks up A's table — bettingOpen: true, committed: [2,1,2,2] — with the warning cleared. Audit and contrast clean, no console errors.

Opening the tool in a second tab — tapping the bookmark again rather than hunting for the tab you already had — **silently throws away whatever the first one is doing.** Stacked on #78. Each tab holds its own copy in memory and each save writes the whole table, so the second one to act wins. Driven with two tabs on one profile: ``` tab A: deal, and Ann calls stored -> bettingOpen true, committed [0,1,2,2] tab B: type a name in seat 5 stored -> bettingOpen false, committed [0,0,0,0] ``` The deal, the blinds and the call are gone, and neither tab said anything. That's the same silent shape as the save and load failures either side of this change. ## The browser already tells us A `storage` event fires in every *other* tab when the key changes, and never in the one that wrote — so our own saves can't trip it. A tab that sees its table move underneath it now says so, once, with the way out attached: > **toast:** This table is open in another tab. Whichever acts last wins. `[Reload]` > > **panel:** This table is open in another tab, and both are writing to it — whichever acts last wins, so work done in the other one can vanish. Close one, then reload this tab to pick up the table as it stands. **Watched rather than merged, deliberately.** Replacing the table under a dealer's hands in the middle of a hand would be its own hazard, and reloading is the only resolution that doesn't throw somebody's work away — so it's offered rather than taken. ## Validation **6 tests (269 total)**: a write from elsewhere is noticed, another app's key and our own recovery key aren't our business, ten writes produce one warning, watching twice listens once, no listener isn't an error, and no `window` at all isn't an error. Driven with two live tabs: both quiet at first, A deals and B warns with the reload offer, **A stays quiet about its own writes**, two more actions in A add no further toasts in B, and reloading B picks up A's table — `bettingOpen: true`, `committed: [2,1,2,2]` — with the warning cleared. Audit and contrast clean, no console errors.

jheaps added 1 commit 2026-09-01 18:35:51 -06:00

Notice when the same table is open twice 4cc8faf8cb

Opening the tool in a second tab -- tapping the bookmark again rather than hunting for
the tab you already had -- silently throws away whatever the first one is doing.

Each tab holds its own copy in memory and each save writes the whole table, so the
second one to act wins. Driven with two tabs on one profile:

  tab A: deal, and Ann calls    stored -> bettingOpen true, committed [0,1,2,2]
  tab B: type a name in seat 5  stored -> bettingOpen false, committed [0,0,0,0]

The deal, the blinds and the call are gone, and neither tab said anything. That is the
same silent shape as the save and load failures either side of this change.

The browser already tells us: a storage event fires in every other tab when the key
changes, and never in the one that wrote. So a tab that sees its table move underneath
it now says so, once, with the way out attached:

  toast:  "This table is open in another tab. Whichever acts last wins."  [Reload]
  panel:  "This table is open in another tab, and both are writing to it — whichever
           acts last wins, so work done in the other one can vanish. Close one, then
           reload this tab to pick up the table as it stands."

Watched rather than merged, deliberately. Replacing the table under a dealer's hands
in the middle of a hand would be its own hazard, and reloading is the only resolution
that does not throw somebody's work away -- so it is offered rather than taken.

6 tests (269 total): a write from elsewhere is noticed, another app's key and our own
recovery key are not our business, ten writes produce one warning, watching twice
listens once, no listener is not an error, and no window at all is not an error.

Driven with two live tabs: both quiet at first, A deals and B warns with the reload
offer, A stays quiet about its own writes, two more actions in A add no further toasts
in B, and reloading B picks up A's table -- bettingOpen true, committed [2,1,2,2] --
with the warning cleared. Audit and contrast clean, no console errors.

Co-Authored-By: Claude Opus 5 <[email protected]>
Claude-Session: https://claude.ai/code/session_015bnp7xKUPFFSpwkYNFaPgb

jheaps referenced this pull request

2026-09-01 18:55:16 -06:00

Take the broken wordmark off the felt #80

jheaps closed this pull request

2026-09-02 09:57:55 -06:00

Pull request closed

Please reopen this pull request to perform a merge.

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: jheaps/JoshHeaps.Net#79