kayg/calternal-v0

Archived

Watch

Fork 0

Calendar Tab: Event pointer drag leaves ghost without saving #1323

Closed

opened 2026-10-07 05:48:09 +00:00 by kayg · 5 comments

kayg commented

2026-10-07 05:48:09 +00:00

Owner

Steps

Run apps/web/e2e/calendar-drag-1015.mjs with a real production build and the local server.
Create the writable CalDAV Event fixture Drag Event on 2026-08-10.
Open its Day view, drag the Event by 30 minutes, and release.

Expected

The Event drag commits through the Calendar API, the Event stays at the dropped time, and the standard Undo action appears.

Actual

At 1440 x 1000, pointerdown and movement reach the Event. The .block.plan.moving ghost appears. At pointerup, the document sees a DIV target instead of the Event; no Event GET or PUT request follows, and the ghost remains without a commit. The committed regression runner times out waiting for the Event API response.

Evidence

Screenshot: artifacts/bash-calendar/round2-drag-debug/event-drag-timeout.png
Pointer and request summary: artifacts/bash-calendar/round2-drag-debug/event-drag-diagnostic.txt

Severity: major.

This appears to be in the shared TimeGrid pointer handling (packages/ui), outside the Calendar Tab job's allowed files. Please route it to the shared UI owner.

## Steps 1. Run `apps/web/e2e/calendar-drag-1015.mjs` with a real production build and the local server. 2. Create the writable CalDAV Event fixture `Drag Event` on 2026-08-10. 3. Open its Day view, drag the Event by 30 minutes, and release. ## Expected The Event drag commits through the Calendar API, the Event stays at the dropped time, and the standard Undo action appears. ## Actual At 1440 x 1000, pointerdown and movement reach the Event. The `.block.plan.moving` ghost appears. At pointerup, the document sees a `DIV` target instead of the Event; no Event GET or PUT request follows, and the ghost remains without a commit. The committed regression runner times out waiting for the Event API response. ## Evidence Screenshot: `artifacts/bash-calendar/round2-drag-debug/event-drag-timeout.png` Pointer and request summary: `artifacts/bash-calendar/round2-drag-debug/event-drag-diagnostic.txt` Severity: major. This appears to be in the shared TimeGrid pointer handling (`packages/ui`), outside the Calendar Tab job's allowed files. Please route it to the shared UI owner.

kayg referenced this issue

2026-10-07 05:48:16 +00:00

Bug bash: calendar #1214

kayg commented

2026-10-07 07:49:11 +00:00

Author

Owner

Round 2 also isolated the pointer resize edge on the same real production Event fixture. Dragging the Event's bottom edge changed its optimistic geometry (height 47.9 px → 48.7 px) and left the card lifted, but no PUT reached /api/v1/calendar/events/ within 30 seconds. The card did not settle or persist. Pointer trace: artifacts/bash-calendar/round2-pointer-resize/; diagnostic output was captured by the runner before its response timeout. This shares the TimeGrid pointer path and the same file ownership boundary as the move symptom.

Round 2 also isolated the pointer resize edge on the same real production Event fixture. Dragging the Event's bottom edge changed its optimistic geometry (`height` 47.9 px → 48.7 px) and left the card lifted, but no PUT reached `/api/v1/calendar/events/` within 30 seconds. The card did not settle or persist. Pointer trace: `artifacts/bash-calendar/round2-pointer-resize/`; diagnostic output was captured by the runner before its response timeout. This shares the TimeGrid pointer path and the same file ownership boundary as the move symptom.

kayg commented

2026-10-07 07:49:20 +00:00

Author

Owner

Correction: the runner preserved artifacts/bash-calendar/round2-pointer-resize/event-drag-timeout.png and printed the pointer/geometry diagnostic to its stdout. It did not save a separate trace or diagnostic file before the 30-second response timeout.

Correction: the runner preserved `artifacts/bash-calendar/round2-pointer-resize/event-drag-timeout.png` and printed the pointer/geometry diagnostic to its stdout. It did not save a separate trace or diagnostic file before the 30-second response timeout.

kayg referenced this issue

2026-10-07 08:45:55 +00:00

Bug bash: calendar #1214

kayg referenced this issue

2026-10-08 02:42:51 +00:00

Bug bash round 3: calendar #1394

kayg referenced this issue

2026-10-08 04:12:42 +00:00

Bug bash round 3: calendar #1394

kayg commented

2026-10-08 05:45:51 +00:00

Author

Owner

Start: branch job/ghost-1323 from dev d395b6e25

Start: branch job/ghost-1323 from dev d395b6e25

kayg commented

2026-10-08 06:21:18 +00:00

Author

Owner

Fixed on job/ghost-1323, head 71fe5922c. Root cause: pullDown (packages/ui/src/gestures.ts) on #route-content claimed the mouse pointer mid-drag at scroll-top and stole the capture from the dragged block, so the block never got pointerup (ghost, no save). It now yields when a descendant holds the capture. Also: dropped Event blocks skip the height spring (one snap-back frame); the drag runner returned to Month before its Log touch proof. Regression: gestures.svelte.test.ts (fails before, passes after) and apps/web/e2e/calendar-drag-1015.mjs passes end to end (mouse, Month touch, keyboard, same-day, cross-day Week, refused write rollback). bun run check rc=0, bun run test 297 files / 2117 tests passed. Screenshots in artifacts/ghost-1323/after (not committed).

Fixed on job/ghost-1323, head 71fe5922c. Root cause: pullDown (packages/ui/src/gestures.ts) on #route-content claimed the mouse pointer mid-drag at scroll-top and stole the capture from the dragged block, so the block never got pointerup (ghost, no save). It now yields when a descendant holds the capture. Also: dropped Event blocks skip the height spring (one snap-back frame); the drag runner returned to Month before its Log touch proof. Regression: gestures.svelte.test.ts (fails before, passes after) and apps/web/e2e/calendar-drag-1015.mjs passes end to end (mouse, Month touch, keyboard, same-day, cross-day Week, refused write rollback). bun run check rc=0, bun run test 297 files / 2117 tests passed. Screenshots in artifacts/ghost-1323/after (not committed).

kayg referenced this issue from a commit

2026-10-08 06:23:06 +00:00

Calendar: pull-to-refresh no longer steals a dragged Event's pointer capture (#1323)

kayg referenced this issue from a commit

2026-10-08 06:23:06 +00:00

perf: refresh exact pins for GridColumn/TimeGrid edits (#1323)

kayg referenced this issue from a commit

2026-10-08 10:41:40 +00:00

Merge job/ghost-1323 (#1323)

kayg referenced this issue from a commit

2026-10-08 10:41:40 +00:00

Merge job/ticks-1361 (#1361 #1428)