Mailing-List: contact dev-help@cordova.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cordova.apache.org
Received-SPF: pass (athena.apache.org: domain of simon.macdonald@gmail.com
 designates 209.85.160.47 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <CAOBL_k7MPLtJveGOb1WgLxABmvfxTzxrf=Km++VoUtqTbyj60w@mail.gmail.com>
References: 
 <CAOBL_k7MPLtJveGOb1WgLxABmvfxTzxrf=Km++VoUtqTbyj60w@mail.gmail.com>
From: Simon MacDonald <simon.macdonald@gmail.com>
Date: Thu, 25 Oct 2012 22:05:19 -0400
Message-ID: 
 <CAM1AYQDRUU=dhHBuSsgqd_W1pYiUzgrJRKFhdxeHMqg6nCtanQ@mail.gmail.com>
Subject: Re: Notification API: notification.confirm: What should this do on
 cancel?
To: dev@cordova.apache.org
Content-Type: multipart/alternative; boundary=047d7b15af47a1b2ae04ccecc1fc

--047d7b15af47a1b2ae04ccecc1fc
Content-Type: text/plain; charset=ISO-8859-1

I think 0 on a cancel is okay as long as we document it. The only other
thing we could do is to add an optional cancellation callback to the end of
the argument list for the method.

Simon Mac Donald
http://hi.im/simonmacdonald


On Thu, Oct 25, 2012 at 5:12 PM, Joe Bowser <bowserj@gmail.com> wrote:

> Hey
>
> I'm working through CB-1742, and adding the onCancel listeners for
> when someone uses the back button.  However, it seems that we don't
> have any behaviour defined for this.  Right now, I return 0 for this
> on the notification.confirm, but I don't think that's right.  What
> should this be?
>
> Any ideas?
>
> Joe
>

--047d7b15af47a1b2ae04ccecc1fc--