W3C home > Mailing lists > Public > whatwg@whatwg.org > September 2014

Re: [whatwg] Notifications and service workers

From: Jonas Sicking <jonas@sicking.cc>
Date: Mon, 29 Sep 2014 04:40:09 -0700
Message-ID: <CA+c2ei-F8h+yVLWT6zOutVC+HNZ8zUTuFnCfjuwDrkZGJ9C=bA@mail.gmail.com>
To: Andrew Wilson <atwilson@google.com>
Cc: WHATWG <whatwg@whatwg.org>, "Tab Atkins Jr." <jackalmage@gmail.com>, Jake Archibald <jaffathecake@gmail.com>, Robert Bīndar <robertbindar@gmail.com>, Peter Beverloo <beverloo@google.com>
On Mon, Sep 29, 2014 at 4:35 AM, Andrew Wilson <atwilson@google.com> wrote:
> I'm sorry, I meant that you can only use the 'data' attribute, if the data
> you want to associate with the notification is structured-cloneable. Which
> precludes lots of interesting stuff, like objects with attached methods,
> memoized functions, etc.
>
> I'm aware that 'data' is structured-cloneable - I'm saying that's not
> sufficient for many uses.

But if the data that you want to associate with the notification isn't
structured clonable, how are you going to make that data survive a
page reload? Keep in mind that for persistent notifications, the
notification often outlives the page that created the notification.

It might help to have some concrete examples of what you're trying to do here.

/ Jonas
Received on Monday, 29 September 2014 11:41:04 UTC

This archive was generated by hypermail 2.3.1 : Monday, 13 April 2015 23:09:31 UTC