Skip to content

Fix attendee response links and focus saved availability on return - #81

Merged
jasrasr merged 1 commit into
mainfrom
fix/availability-response-recovery
Sep 24, 2026
Merged

jasrasr merged 1 commit into
mainfrom
fix/availability-response-recovery

Conversation

@jasrasr

@jasrasr jasrasr commented Sep 18, 2026

Copy link
Copy Markdown
Owner

Problem

Attendee recovery links did not explicitly select attendee mode, so locally remembered admin credentials could override the attendee's response context. Removing the URL fragment also dropped the invite mode on reload. The recovery link appeared in the organizer's top-of-page link panel rather than under the attendee's Save button.

Changes

  • Generate response links with view=response; legacy response fragments also force attendee mode and take precedence over saved admin/response credentials.
  • Preserve attendee/response mode on sanitized URLs and reloads while retaining the original admin recovery token in browser storage.
  • Keep the response token fragment when storage is blocked so a reload can still recover the response.
  • Move the private response link directly below Save my availability, outside the disabled voting form so closed/expired polls still permit copying it.
  • Focus and scroll to Your availability once after successful saved-response recovery; background polling does not steal focus or scrolling.
  • Bump to v1.3.2 with updated asset URLs, changelog, documentation and a reusable browser regression suite.

Validation

  • PHP/JavaScript syntax and git diff checks passed.
  • Chromium browser suite passed: old/new links, fresh browser, event passwords, stale stored admin credentials, reloads, restored private contacts/headcounts/food/answers, editing without duplicate responses, blocked localStorage, exact link placement, one-time focus/scroll, and closed-poll copying.
  • Existing server authorization and password requirements remain enforced; an attendee link never gains admin access.

Deployment

Merge and let the host sync source. No runtime event data changes. Live deployment has not yet been verified.

@jasrasr
jasrasr merged commit 2902228 into main Sep 24, 2026
1 check passed
@jasrasr
jasrasr deleted the fix/availability-response-recovery branch September 24, 2026 22:47
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