Skip to content

fix: guard crypto.randomUUID for non-secure HTTP contexts#171

Merged
jlunder00 merged 13 commits intofeature/calendar-tabfrom
main
Apr 24, 2026
Merged

fix: guard crypto.randomUUID for non-secure HTTP contexts#171
jlunder00 merged 13 commits intofeature/calendar-tabfrom
main

Conversation

@jlunder00
Copy link
Copy Markdown
Owner

Summary

  • useSlideOver.ts: replace bare crypto.randomUUID() in decodeStack() and push() with crypto.randomUUID?.() ?? (Math.random().toString(36).slice(2) + Date.now().toString(36))
  • events.ts: same guard on the optimistic local event ID (line 48)
  • SlideOverStack.vue: fix pre-existing type error — pointerEvents cast to 'auto' | 'none' so vue-tsc accepts it (this was blocking npm run build on the base branch)

Why

crypto.randomUUID() requires a secure context (HTTPS / localhost). The Pi is accessed via Tailscale IP over plain HTTP, so the call throws, breaking task card clicks in KanbanView.

Test plan

  • npm run build — zero type errors ✅
  • Click task card on Pi over HTTP — slide-over panel opens without TypeError
  • Restore ?panels= query param on page load — no crash

@jlunder00 jlunder00 merged commit 9361d48 into feature/calendar-tab Apr 24, 2026
6 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant