Re: Different behavior when clicking the notification with a set tag

Hi Peter,
thank you for the reply.

I tested this behavior in Chrome 34 on Windows (vs Firefox on Windows)
using this demo (
http://aurelio.audero.it/demo/web-notifications-api-demo.html). I can
confirm that what I was talking about is exactly the issues you've outlined
and that you've reported. I was able to reproduce them following your steps.

This will be my last reply as this is a browser-specific issue and not
something related with the specs. Let's continue the discussion there.

Have a nice day


2014-04-23 14:35 GMT+01:00 Peter Beverloo <beverloo@google.com>:

> Hi Aurelio,
>
> Out of interest, which platform were you testing on? I notice some recent
> changes in behavior when using Chrome on Ubuntu, most notably that clicking
> on a notification now closes it without firing the close() event. This may
> apply to other platforms as well.
>
> I created the following test-case to try and reproduce your problem:
>   http://jsbin.com/notification-tag/1
>
> First click on the Permission button to grant permission, if required,
> then display a few notifications. You should see the existing notification
> being replaced. Click on the displayed notification, which now makes it
> disappear. I notice that (a) Chrome is not firing the appropriate close()
> events, and (b) clicking on the Display button doesn't do anything anymore,
> until you click on the Close button.
>
> I filed the following bugs against our implementation, and will look into
> getting them fixed soon!
>
>   https://code.google.com/p/chromium/issues/detail?id=366098 (not firing
> the close() event)
>   https://code.google.com/p/chromium/issues/detail?id=366100 (not showing
> replaceable notifications after clicking on one)
>   https://code.google.com/p/chromium/issues/detail?id=366102 (clicking on
> a notification now closes it)
>   https://code.google.com/p/chromium/issues/detail?id=366104(notifications stay open after navigating away)
>
> Arguably these bugs would be a more appropriate forum for discussing
> browser-specific issues than this mailing list, but since you were in doubt
> this is fine. Thank you very much for reaching out :-)!
>
> Thanks,
> Peter
>
>
> On Wed, Apr 23, 2014 at 12:30 PM, Aurelio De Rosa <aurelioderosa@gmail.com
> > wrote:
>
>> Hello.
>>
>> In writing an article on the Web Notifications API (
>> http://www.sitepoint.com/introduction-web-notifications-api/), I noticed
>> a different behavior in Chrome and Firefox. An user who read the same
>> article, has noticed it too. The difference is that once a user clicks on a
>> notification with a set tag, while Chrome don't show any new notification
>> with the same tag, Firefox does.
>>
>> Based on my understanding of the specifications, they don't define what
>> to do in this case (but I may be wrong). Therefore, I'm not sure if this is
>> an issue of a specific browser (Chrome or Firefox) or a hole in the
>> specifications (maybe intentional?).
>>
>> Anyway, I thought it'd be nice to report it here.
>>
>> Cheers
>>
>> --
>> Aurelio De Rosa
>> email: aurelioderosa@gmail.com
>> email:  a.derosa@audero.it
>> website: www.audero.it
>> skype: AurelioDeRosa
>>
>
>


-- 
Aurelio De Rosa
email: aurelioderosa@gmail.com
email:  a.derosa@audero.it
website: www.audero.it
skype: AurelioDeRosa