Re: Push API change for permissions UX

 Example https://www.youtube.com/watch?v=0i7YdSEQI1w - Twitter shows
notifications without caching, creating a poor offline (or poor
connectivity) experience. You can actually be left with less information
after tapping the notification than before.

On 26 October 2014 06:42, Jake Archibald <jaffathecake@gmail.com> wrote:

> This discussion is about how often push may be processed silently (without
> showing a notification), not if a push notification may *only* show a
> notification.
>
> The latter was shown to be insufficient in the other thread.
> On Fri, Oct 24, 2014 at 9:39 AM, Owen Campbell-Moore <owencm@google.com>
> wrote:
> >> I think it might make sense to ask for permission to display
> >> notifications/UI at the same time as you ask for permission to "run in
> the
> >> background".
> >
> > I hope the above explains why we believe that while some sites may want
> to
> > ask for both permissions, they should be able to say to the user "Hey, I
> > want to send you notifications", without saying "Hey, I want to run in
> the
> > background whenever I want for any reason".
>
> I suggest that if we attempt to solve this use case, that we do it by
> adding the ability to send push messages that directly create a
> notification, without waking up a SW.
>
> There's recently been a separate thread about that.
>
> / Jonas
>
>