Web app does not fire task/due date notifications in Chrome (self-hosted)

[thecoffeebin]

I'm using the self-hosted web version of Mindwtr (latest Docker images) in Google Chrome.

Everything appears to work as expected except for notifications.

Environment
Deployment: Self-hosted (mindwtr-app + mindwtr-cloud)
Browser: Google Chrome (latest)
OS: Windows (work laptop)
Accessing via HTTPS

Steps to reproduce
Create a task with a due date/time a few minutes in the future.
Ensure Task reminders and Due date reminders are enabled in Settings.
Grant Chrome permission to display notifications for the site.
Wait until the scheduled reminder time.

Expected behavior

A browser notification should be displayed when the reminder or due time is reached.

Actual behavior

No notification is displayed.

Additional information
Chrome notifications are working correctly for other websites/applications.
The site has notification permission enabled.
Tasks and syncing otherwise work normally.
There are no obvious errors shown in the UI.

Unfortunately I'm unable to test the desktop version of Mindwtr because I'm using a managed work laptop and Windows blocks the application from running ("Don't run"), so I'm relying on the web application as my primary interface.

Could you confirm whether browser notifications are currently supported in the self-hosted web app, or if this is a bug?

[thecoffeebin]

I noticed the reminder scheduler appears to exist only in apps/desktop/src/lib/notification-service.tsx, where checkDueAndNotify() polls every 15 seconds and ultimately calls new Notification(). I couldn't find an equivalent scheduler for the web app. Browser notifications themselves work (Notification.permission === "granted" and new Notification() from DevTools succeeds), but task reminders never fire in the self-hosted web application. Is this an intentional limitation, or is the reminder scheduler missing from the web build?

[dongdongbh]

Bug, not a limitation — and your reading was almost exactly right. The scheduler isn't missing from the web build; notification-service.tsx ships in it and already falls back to new Notification() when the Tauri plugin isn't there. What was wrong is one line up the stack: App.tsx started it inside an if (isTauriRuntime()) block, alongside the file watchers that genuinely do need the native shell. So on web the service was present, permission was granted, and nothing ever called startDesktopNotifications().

Fixed in 0256579. I checked it against a browser rather than just the tests: a task due 20 seconds out fires "Call the dentist / Due date reminders", and reverting just that line makes it silent again.

One thing you'll want to know before relying on it. The scheduler is a 15-second poll inside the page, so reminders only arrive while a Mindwtr tab is open, and Chrome throttles a background tab's timers to roughly one a minute. The poll used to only fire a reminder in the 15 seconds before its time, which would have missed most of them in a background tab, so it now also covers whatever gap has passed since the previous check (capped at five minutes, deduped so nothing fires twice). A reminder reached with every tab closed is still skipped rather than delivered later — for those you need the desktop or mobile app.

Worth a separate note given your work laptop: Windows blocking the installer is usually SmartScreen on the unsigned build, which #965 is tracking (SignPath is pending). The portable ZIP sometimes gets through where the installer doesn't, if that's useful to you.

The next mindwtr-app image will have this — let me know whether reminders land for you there.