[horde] Browser notification keeps nagging

Jan Schneider jan at horde.org
Sat Jun 25 13:24:39 UTC 2016

Zitat von Daniel Kraus <dk at doktorkraus.de>:

> On Thu Jun 23 2016 10:45:13 GMT+0200 (CEST), Jan Schneider
> <jan at horde.org> wrote:
>> Zitat von Daniel Kraus <dk at doktorkraus.de>:
>>> On Thu Jun 23 2016 09:17:57 GMT+0200 (CEST), Jan Schneider
>>> <jan at horde.org> wrote:
>>>> Zitat von Daniel Kraus <dk at doktorkraus.de>:
>>>>> On Wed Jun 22 2016 16:11:47 GMT+0200 (CEST), Jan Schneider
>>>>> <jan at horde.org> wrote:
>>>>>> Zitat von Daniel Kraus <dk at doktorkraus.de>:
>>>>>>> Dear all,
>>>>>>> the browser notification for a Horde task keeps nagging me.
>>>>>>> The task is definitively marked as completed, and even the due date
>>>>>>> that
>>>>>>> I had set has passed. Still, the browser notifications for this
>>>>>>> particular task keep appearing with every click in Horde.
>>>>>>> What am I missing, how can I turn this off (without generally
>>>>>>> blocking
>>>>>>> browser notifications from Horde)?
>>>>>>> Thanks in advance.
>>>>>>> Daniel
>>>>>> Dismiss the notification? Also make sure that this isn't a recurring
>>>>>> task.
>>>>> Thanks for the response. No, it wasn't a recurring task. But here's a
>>>>> very strange observation: The notifications kept popping up with
>>>>> Chromium 50.0.2661.102 (Ubuntu 16.04). When I visited the site with
>>>>> Firefox 47.0, the notification (for the completed, historical task)
>>>>> appeared once, but never again after dismissing it. Interestingly,
>>>>> going
>>>>> back to Chromium, the notification no longer appeared either!
>>>>> So, the problem is solved, but the question remains for me why Chromium
>>>>> doesn't properly dismiss notifications, but accepts when another
>>>>> browser
>>>>> has dismissed one.
>>>>> Daniel
>>>> We do talk about the horde-style notifications in the bottom right
>>>> corner, right? Not about the desktop notifications.
>>> No, not the ones in the bottom-right corner, but the browser desktop
>>> notifications.
>>>> Do you see any Javascript errors in the browser console? Or any errors
>>>> in the horde/PHP logs?
>>> No errors in the browser console or in the server logs.
>>> I can reproduce this with new tasks: Set the due date to this morning,
>>> enable reminder, mark the task as done, and the notifications keep
>>> appearing, even when I log into Horde with another browser that has
>>> never seen this task in the 'active' state. There should be no
>>> notifications for completed tasks -- I believe this might be an issue
>>> with Horde.
>>> Only when I check "done" in the initial task creation form, I will never
>>> get to see notifications.
>> This is a bug in Chrome then.
> Except I can reproduce it with Firefox on Ubuntu. Moreover, this
> morning, when logging into Horde using Firefox (which is not my default
> browser), I saw a whole bunch of notifications for test tasks that I had
> created and marked completed yesterday.
>>> (Another, browser-related usability problem that I discovered is this:
>>> When notifications are 'dismissed' by clicking the X in the top-right
>>> corner, the keep re-appearing. They can be dismissed for good by
>>> clicking into the client area of the notification. This won't give any
>>> visual feedback in either Chromium or Firefox, but afterwards the
>>> notification is gone for good.)
>> Desktop notifications don't allow interaction back to the server. Horde
>> isn't notified about dismissed desktop notifications.
> It's probably not so much about dismissing than about triggering a
> notification. I guess if browsers remember that a site had requested to
> show a notification, they could keep showing it even if the site no
> longer 'asks' to display the desktop notifications. But:
> The fact that one browser displays desktop notifications for a task that
> has been created and subsequently marked completed in an entirely
> different browser suggests that Horde triggers desktop notifications for
> completed tasks.

I have lost a bit track about which notification is showing where and  
which task had been created and closed in which client.
Can you provide a single, simple, reproducible set of steps that  
triggers this behavior always for you?

Jan Schneider
The Horde Project

More information about the horde mailing list