spikerj/spikersoft-issues
1
0 Fork 0
Code Issues 23 Pull Requests Actions Packages Projects Releases Wiki Activity

enhancement: Calendar location field needs autocompletion and suggestions for accessibility #108

New Issue
Closed
opened 2026-05-11 15:00:20 +00:00 by enjin2310 · 1 comment
enjin2310 commented 2026-05-11 15:00:20 +00:00
Copy link
Copy source

The Location field in the calendar's "Edit Event" dialog is not fully functional and lacks accessibility features.

Observed behavior:

  • The Location input field appears to accept text but does not respond as expected.
  • No autocompletion suggestions are provided when users type a location.
  • No location suggestions or dropdown appear to help users select from common or previously used locations.
  • The attached screenshot shows the Location field with only placeholder text "Enter event location".

Expected behavior:

  • The Location field should be fully functional and responsive.
  • When users start typing, the field should display autocomplete suggestions.
  • Previously used locations or a location database should be queried to provide helpful suggestions.
  • A dropdown with location options should appear for better UX and accessibility.

Impact:

  • Users must manually type complete location information without assistance.
  • Reduces accessibility and ease of use for users creating calendar events.
  • Increases typing effort and potential for location entry errors.

Classification:

  • Type: feature / enhancement (missing accessibility feature)
  • Secondary: bug (Location field not fully functional)
  • Area: Calendar / event editing / location input
  • Severity: medium
  • Priority: medium
The Location field in the calendar's "Edit Event" dialog is not fully functional and lacks accessibility features. Observed behavior: - The Location input field appears to accept text but does not respond as expected. - No autocompletion suggestions are provided when users type a location. - No location suggestions or dropdown appear to help users select from common or previously used locations. - The attached screenshot shows the Location field with only placeholder text "Enter event location". Expected behavior: - The Location field should be fully functional and responsive. - When users start typing, the field should display autocomplete suggestions. - Previously used locations or a location database should be queried to provide helpful suggestions. - A dropdown with location options should appear for better UX and accessibility. Impact: - Users must manually type complete location information without assistance. - Reduces accessibility and ease of use for users creating calendar events. - Increases typing effort and potential for location entry errors. Classification: - Type: feature / enhancement (missing accessibility feature) - Secondary: bug (Location field not fully functional) - Area: Calendar / event editing / location input - Severity: medium - Priority: medium
Screenshot 2026-05-11 105656.png
158 KiB
Screenshot 2026-05-11 105656.png
spikerj commented 2026-08-07 13:48:27 +00:00
Owner
Copy link
Copy source

Migrated to spikerj/spikersoft-angular#642 as part of the umbrella-tracker breakup.

Verified 2026-08-07 against spikersoft-angular@8e5a404, and live against the deployed main-KZKZUOSX.js bundle on learn.spikersoft.com.

  • Code: projects/spikersoft/src/app/_components/calendar/event-modal/event-modal.component.html:59-70 — the Location control is a plain matInput bound to [formField]="eventForm.location" with a locationPlaceholder placeholder, a location_on matSuffix icon and a maxLength mat-error. There is no mat-autocomplete, no [matAutocomplete] trigger and no options source anywhere in the component. rg 'locationSuggest|AutocompleteService|placePredictions|placesService' across _components/calendar and _services → 0 hits.
  • Live: learn.spikersoft.com → main-KZKZUOSX.js → lazy chunk-CMGMHm8b2.js (the deployed event-modal) contains locationPlaceholder but 0 occurrences of mat-autocomplete.

Status: not done — The whole enhancement. Note the ticket's secondary "field not fully functional" symptom does look resolved — the input is now signal-forms bound and validated — so the live scope is narrower than filed: add autocomplete/suggestions (previously-used locations and/or a places source) to the Location field. Worth deciding the suggestion source first (own event history vs. Google Places), since spikerj/spikersoft-issues#236 has the Maps JS API pinned to v=3.64.

Closing here. Work now lives in the repo that holds the fix, so fixes #642 in a PR will auto-close it on merge. The umbrella tracker keeps cross-repo epics only.

— Opus 5 Agent

Migrated to **spikerj/spikersoft-angular#642** as part of the umbrella-tracker breakup. Verified 2026-08-07 against `spikersoft-angular@8e5a404`, and live against the deployed `main-KZKZUOSX.js` bundle on learn.spikersoft.com. - **Code:** `projects/spikersoft/src/app/_components/calendar/event-modal/event-modal.component.html:59-70` — the Location control is a plain `matInput` bound to `[formField]="eventForm.location"` with a `locationPlaceholder` placeholder, a `location_on` `matSuffix` icon and a maxLength `mat-error`. There is no `mat-autocomplete`, no `[matAutocomplete]` trigger and no options source anywhere in the component. `rg 'locationSuggest|AutocompleteService|placePredictions|placesService'` across `_components/calendar` and `_services` → 0 hits. - **Live:** `learn.spikersoft.com` → `main-KZKZUOSX.js` → lazy `chunk-CMGMHm8b2.js` (the deployed event-modal) contains `locationPlaceholder` but **0** occurrences of `mat-autocomplete`. Status: **not done** — The whole enhancement. Note the ticket's secondary "field not fully functional" symptom does look resolved — the input is now signal-forms bound and validated — so the live scope is narrower than filed: **add autocomplete/suggestions** (previously-used locations and/or a places source) to the Location field. Worth deciding the suggestion source first (own event history vs. Google Places), since spikerj/spikersoft-issues#236 has the Maps JS API pinned to `v=3.64`. Closing here. Work now lives in the repo that holds the fix, so `fixes #642` in a PR will auto-close it on merge. The umbrella tracker keeps cross-repo epics only. — Opus 5 Agent
Sign in to join this conversation.
No Branch/Tag Specified
Labels
Clear labels
agentic
Actionable surfaced by the agentic architecture & security review
 bug
Something is not working
 duplicate
This issue or pull request already exists
 enhancement
New feature
 epic
Cross-repo epic — children live in per-repo trackers
 help wanted
Need some help
 invalid
Something is wrong
 question
More information is needed
 sonarqube
Code quality issue surfaced by SonarQube (bug / code smell)
 wontfix
This won't be fixed
No labels
Milestone
No items
No Milestone
Projects
Clear projects
No projects
Assignees
Clear assignees
spikerj (Joseph Spiker)
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: spikerj/spikersoft-issues#108