Wire NotificationListItem tap to deep link handler
epic-in-app-notification-centre-ui-task-010 — Connect each NotificationListItem tap gesture in the NotificationCentreScreen to the NotificationDeepLinkHandler. On tap, call handler.navigate(notification.payload) and let the handler resolve and navigate or show the fallback. Ensure the tapped notification is visually marked as read immediately on tap (optimistic UI update) by dispatching MarkNotificationRead to the BLoC before the async navigation resolves. Unread items should have a distinct visual treatment (left accent border, bold title) using design token classes.
Acceptance Criteria
Technical Requirements
Execution Context
Tier 5 - 253 tasks
Can start after Tier 4 completes
Implementation Notes
In NotificationListItem, use an onTap callback rather than embedding navigation logic directly in the widget — keep the widget dumb. In NotificationCentreScreen, provide the onTap as: `onTap: () { if (!notification.isRead) { context.read
AppTextStyles.bodyRegular : AppTextStyles.bodyBold` from the design token system. Do not store `isRead` in local widget state — derive it entirely from the BLoC state to avoid stale UI.
Testing Requirements
Write flutter_test widget tests covering: (1) tapping an unread item dispatches MarkNotificationRead before navigate is called (verify call order with a mock handler), (2) item visual state changes to read immediately after tap, (3) deep link handler called with the correct payload from the tapped notification, (4) deleted entity fallback renders snackbar without crashing, (5) malformed payload triggers fallback gracefully, (6) re-tapping a read item does not dispatch MarkNotificationRead. Use mockito or mocktail to mock NotificationDeepLinkHandler. Verify BLoC state transitions with bloc_test.
If a referenced entity (contact, certification, activity) has been deleted or its RLS policy now excludes the current user, the deep link handler may navigate to a screen that renders in an error state or throws an unhandled exception.
Mitigation & Contingency
Mitigation: The deep link handler must perform a lightweight existence check (HEAD request or minimal SELECT) before pushing the route. Define a contract with each destination screen for how to handle a not-found entity ID passed as a route parameter.
Contingency: If the existence check itself fails (network error), navigate to the destination screen anyway and let it handle the error gracefully with its own error state; do not block navigation for network timeouts.
If the tab badge widget triggers a full rebuild of the bottom navigation bar on every unread count change, it will cause visible jank on devices with many active Realtime events (e.g., org admins receiving org-wide alerts).
Mitigation & Contingency
Mitigation: Scope the badge widget to a dedicated BlocSelector that rebuilds only when the unread count value changes, not on any BLoC state emission. Use RepaintBoundary to isolate the badge from the rest of the nav bar.
Contingency: If performance issues persist, debounce badge updates to a maximum of one rebuild per 500ms and display the last known count during the debounce window.
Complex swipe-to-mark-read gestures and dynamic list updates may conflict with VoiceOver/TalkBack navigation patterns, particularly for Blindeforbundet users who rely exclusively on screen readers.
Mitigation & Contingency
Mitigation: Provide a dedicated accessibility action (Semantics.onTap / CustomSemanticsAction) for mark-as-read on each list item so screen reader users do not need the swipe gesture. Test with VoiceOver on iOS and TalkBack on Android before each release.
Contingency: If the swipe gesture proves incompatible with assistive technologies, disable it when a screen reader is detected (via ScreenReaderDetectionService) and rely solely on the tap-to-read and accessible action pathways.