On Wed, Nov 20, 2013 at 12:45 AM, Jonas Sicking wrote:
> On Tue, Nov 19, 2013 at 5:37 AM, Anne van Kesteren wrote:
>> What are you thinking of? We define some kind of UI hints a developer
>> can register for when initiating a new notification? Might work I
>> suppose.
>
> I think we should have a
On Tue, Nov 19, 2013 at 5:37 AM, Anne van Kesteren wrote:
This may be part of just further defining the steps for the "click"
pathway in the spec, but at least in FirefoxOS right now, the
notification onclick pathway does not bring the app to the visible
front in all cases. The
On Tue, Oct 29, 2013 at 3:51 PM, Jonas Sicking wrote:
> On Tue, Oct 29, 2013 at 8:26 AM, Anne van Kesteren wrote:
>> That seems like an implementation detail. Activation could mean
>> dismissal, but e.g. on Mac OS X activation does not mean dismissal.
>> It's up to the site/app to dismiss after a
On Tue, Oct 29, 2013 at 3:47 PM, Jasper St. Pierre
wrote:
> On Tue, Oct 29, 2013 at 11:26 AM, Anne van Kesteren
> wrote:
>> We currently do not have a way to have events out-of-band for the web.
>
> What about providing a URL that the user-agent will open? If the originating
> tab of the notifica
On Tue, Oct 29, 2013 at 3:43 PM, Jonas Sicking wrote:
> Strings certainly solves the use cases since anything can be encoded
> into a string. However it seems to me that using structured clones
> will make things a lot easier for pages in many cases. This was always
> *the* top complaint about loc
On Tue, Oct 29, 2013 at 8:26 AM, Anne van Kesteren wrote:
> On Fri, Sep 27, 2013 at 2:15 AM, James Burke wrote:
>> 2) General notification callback entry point
>>
>> We are avoiding use of notification.onclick/onclose and would prefer
>> to have a generic entry point to receive notification event
On Tue, Oct 29, 2013 at 11:26 AM, Anne van Kesteren wrote:
> On Fri, Sep 27, 2013 at 2:15 AM, James Burke wrote:
> > 2) General notification callback entry point
> >
> > We are avoiding use of notification.onclick/onclose and would prefer
> > to have a generic entry point to receive notification
On Tue, Oct 29, 2013 at 7:32 AM, Anne van Kesteren wrote:
> On Wed, Oct 16, 2013 at 9:22 PM, James Burke wrote:
>> On Mon, Oct 14, 2013 at 7:09 AM, Anne van Kesteren wrote:
>>> It seems using a structured clone makes the most sense. Transfering
>>> objects won't work here. It's not entirely clea
On Fri, Sep 27, 2013 at 2:15 AM, James Burke wrote:
> 2) General notification callback entry point
>
> We are avoiding use of notification.onclick/onclose and would prefer
> to have a generic entry point to receive notification events. Right
> now we use navigator.mozSetMessageHandler('notificatio
On Wed, Oct 16, 2013 at 9:22 PM, James Burke wrote:
> On Mon, Oct 14, 2013 at 7:09 AM, Anne van Kesteren wrote:
>> It seems using a structured clone makes the most sense. Transfering
>> objects won't work here. It's not entirely clear to me what the best
>> is for Blob, File, etc. Effectively the
On Mon, Oct 14, 2013 at 7:09 AM, Anne van Kesteren wrote:
>
> It seems using a structured clone makes the most sense. Transfering
> objects won't work here. It's not entirely clear to me what the best
> is for Blob, File, etc. Effectively the page can shut down, but they
> will still be kept alive
On Fri, Sep 27, 2013 at 2:15 AM, James Burke wrote:
> 1) Ability to pass data with the Notification
>
> Right now, we URL-encode some args to the iconURL to pass data to the
> handler function that is registered via
> navigator.mozSetMessageHandler('notification', function(){}) [1].
>
> It would b
On Fri, Sep 27, 2013 at 12:54 AM, Andrew Wilson wrote:
> So, I'm not entirely sure how many lessons taken from the FirefoxOS
> implementation are applicable to the API for web pages in general, but I
> agree that "what do we do if the user clicks on a notification after the
> parent page has been
So, I'm not entirely sure how many lessons taken from the FirefoxOS
implementation are applicable to the API for web pages in general, but I
agree that "what do we do if the user clicks on a notification after the
parent page has been closed" is a bit of an unsolved/unsolveable problem
with the cur
This Notifications feedback comes from using them in FirefoxOS for the
email web app. It uses an alarm API to periodically wake up, do an
email sync, and if new messages, creates some Notifications. The web
app may also shut itself down if it was not already opened in a
visible state. The OS may al
15 matches
Mail list logo
