; official
> >> > > > >> > > > > > release process for the plugins?
> >> > > > >> > > > > >
> >> > > > >> > > > > > On Mon, Mar 16, 2015 at 11:17 PM, Ian Clelland <
> >> > > > >> > > iclell...@chromium.org
> >> > > > >> > >
gt; > wrote:
>> > > > >> > > > > >
>> > > > >> > > > > > > +1 -- Let's get this out the door :)
>> > > > >> > > > > > > I'll see what I can get done to move it in that
>> > direction.
>> > > > >> > > > > > >
>
publishing
> > > > >> > > whitelist
> > > > >> > > > > > >> plugins, and making it so that the default project
> > > template
> > > > >> > > includes
> > > > >> > > > > > >> ). Maybe
&
erge Huijben [mailto:s.huij...@gmail.com]
> Sent: Thursday, April 9, 2015 11:47 AM
> To: Ian Clelland; dev@cordova.apache.org
> Cc: leo.treggi...@intel.com
> Subject: Re: [DISCUSS] Cordova-Android 4.0.0 Release
>
> Then, it seems strange to me that it logs an error and repeated warnings
&g
;> > > > > > > I'll see what I can get done to move it in that
> >> direction.
> >> > > >> > > > > > >
> >> > > >> > > > > > > On Mon, Mar 16, 2015 at 7:51 PM, Andrew Grieve <
> >> &
: leo.treggi...@intel.com
Subject: Re: [DISCUSS] Cordova-Android 4.0.0 Release
Then, it seems strange to me that it logs an error and repeated warnings if the
meta tag is missing. Perhaps we should remove that from the plugin.
Op do 9 apr. 2015 om 20:21 schreef Ian Clelland
> Moving from [V
; > > > > > >> Everything's ready afaik (minus upgrade guide,
>> publishing
>> > > >> > > whitelist
>> > > >> > > > > > >> plugins, and making it so that the default project
>
> > >> > > > while
> > > >> > > > > > we
> > > >> > > > > > >> wait on these things being finished up?
> > > >> > > > > > >>
> > > >> > >
rieve
Sent: Wednesday, April 08, 2015 7:08 PM
To: Andrew Grieve
Cc: dev; Homer, Tony
Subject: Re: [DISCUSS] Cordova-Android 4.0.0 Release
CB-8684 is now merged and I've updated the targetSdk (and made a couple
other changes).
I'll start the release process in the morning as long as ther
t; awesome.
> > >> > > > > > >>
> > >> > > > > > >> On Mon, Mar 16, 2015 at 4:57 PM, Shazron <
> > shaz...@gmail.com>
> > >> > > wrote:
> > >> > > > > > >>
> > >>
> >> > > > > > >> > +1 for vote thread, let's get this thing out so people
> >> (that
> >> > are
> >> > > > not
> >> > > > > > >> > us) can test...
> >> > &g
t; > > > > > >> >
>> > > > > > >> > On Mon, Mar 16, 2015 at 1:41 PM, Joe Bowser <
>> > bows...@gmail.com>
>> > > > > > wrote:
>> > > > > > >> > > OK, this is a three month old thread, and we'r
; >> > On Mon, Mar 16, 2015 at 1:41 PM, Joe Bowser <
> > bows...@gmail.com>
> > > > > > wrote:
> > > > > > >> > > OK, this is a three month old thread, and we're waiting
> on a
> > > > > > >> discussion
> > > > > > >> > > before we re
gacy whitelist plugin and a new style
> > > > whitelist
> > > > > >> > > plugin. We shouldn't keep constantly delaying this release
> > > > because
> > > > > of
> > > > > >> > > what'
> > >> > > plugin. We shouldn't keep constantly delaying this release
> > > because
> > > > of
> > > > >> > > what's happening on other platforms, especially since we
> already
> > > > >> > pluginized
t; > > the whitelist.
> > > >> > >
> > > >> > > Can we please release soon?
> > > >> > >
> > > >> > > On Thu, Mar 12, 2015 at 2:20 PM Nikhil Khandelwal <
> > > >> > nikhi...@microsoft.com&
> > >> > >
> > >> > >> I know we discussed a couple of approaches implementing the
> default
> > >> > >> whitelist policy for Android/iOS - either every app would be
> > >> required to
> > >>
gt; >> I know we discussed a couple of approaches implementing the default
> >> > >> whitelist policy for Android/iOS - either every app would be
> >> required to
> >> > >> include the whitelist plugin or have it have smart defaults in
app would be
>> required to
>> > >> include the whitelist plugin or have it have smart defaults in the
>> > platform
>> > >> implementation and the plugin being able to override them.
>> > >>
>> > >> I don’t think that threa
able to override them.
> > >>
> > >> I don’t think that thread closed with any conclusions.
> > >>
> > >> Thanks,
> > >> Nikhil
> > >>
> > >>
> > >> -Original Message-
> > >> From: Jo
; >>
> >> I don’t think that thread closed with any conclusions.
> >>
> >> Thanks,
> >> Nikhil
> >>
> >>
> >> -Original Message-
> >> From: Joe Bowser [mailto:bows...@gmail.com]
> >> Sent: Thursday, March 1
rt defaults in the platform
>> implementation and the plugin being able to override them.
>>
>> I don’t think that thread closed with any conclusions.
>>
>> Thanks,
>> Nikhil
>>
>>
>> -Original Message-----
>> From: Joe Bowser [m
iginal Message-
> From: Joe Bowser [mailto:bows...@gmail.com]
> Sent: Thursday, March 12, 2015 11:23 AM
> To: dev
> Subject: Re: [DISCUSS] Cordova-Android 4.0.0 Release
>
> OK, so right now it's just docs? How soon can we get a VOTE thread started
> for 4.0.0?
>
&
that thread closed with any conclusions.
Thanks,
Nikhil
-Original Message-
From: Joe Bowser [mailto:bows...@gmail.com]
Sent: Thursday, March 12, 2015 11:23 AM
To: dev
Subject: Re: [DISCUSS] Cordova-Android 4.0.0 Release
OK, so right now it's just docs? How soon can we get a VOTE t
OK, so right now it's just docs? How soon can we get a VOTE thread started
for 4.0.0?
On Wed, Mar 4, 2015 at 10:47 AM Andrew Grieve wrote:
> mobilespec is now working again... Took longer than I would have liked, but
> did you know that on Android FileReader triggers shouldInterceptRequest()
> w
mobilespec is now working again... Took longer than I would have liked, but
did you know that on Android FileReader triggers shouldInterceptRequest()
with Blob URLs!?
Separate thread is already happening re: whitelists, so once that's figured
out, it's just docs afaict.
On Mon, Mar 2, 2015 at 10:
On Mon, Mar 2, 2015 at 6:00 PM, Jesse wrote:
> We should start a new whitelist plugin related thread.
>
> Why is a plugin blocking a release? Default (aka no-plugin) behavior
> should be to allow all network requests shouldn't it?
Well, that just might be a blacklist then :)
> This thread
I'm just about finished working through fixing mobilespec to work with the
latest whitelist changes. Once I've figured out things, I'll kick up a
discuss about how it works. Right now, on master, all network requests are
blocked without a plugin enabling them. But I think we should discuss
whether
We should start a new whitelist plugin related thread.
Why is a plugin blocking a release? Default (aka no-plugin) behavior
should be to allow all network requests shouldn't it? This thread is a
month long, and not the first discussion of 4.0.0 for Android.
@purplecabbage
risingj.com
On Mon, M
Why do we need both the legacy and new-style whitelists released before we
do a cordova-android 4.0.x release? Is there something that the new-style
whitelist needs to change in the API that would force us to do a 5.0.x
release?
On Mon Mar 02 2015 at 2:04:59 PM Shazron wrote:
> legacy-whitelist-
legacy-whitelist-plugin should be fixed so that it compiles on
cordova-ios@3.8.0. It shouldn't be a problem to fix this at compile or
run-time (whichever is applicable here related to the compile error)
On Mon, Mar 2, 2015 at 1:47 PM, Darryl Pogue wrote:
> On 2 March 2015 at 13:37, Joe Bowser wr
On 2 March 2015 at 13:37, Joe Bowser wrote:
> So, right now the whitelist changes are what's holding up the 4.0.0 release
> now? Is this really the only thing that's holding up this release?
>
> On Wed Feb 25 2015 at 1:18:26 PM Andrew Grieve wrote:
>
>> I think we'll also need to finish with the
o...
> > >> > > > I
> > >> > > > > > think we'd be fine (and should) delete our top-level
> > >> LinearLayout.
> > >> > > > > Plugins
> > >> > > > > > and emb
.
> >> > > > > >
> >> > > > > > Still waiting on a tools release for 3.7.1.
> >> > > > > > Still need to update platform docs for 4.0.0
> >> > > > > >
> >> > > > > > But... I think that's
> > > >
>> > > > > > On Wed, Feb 4, 2015 at 10:11 PM, Ian Clelland <
>> > > iclell...@chromium.org>
>> > > > > > wrote:
>> > > > > >
>> > > > > > > On Wed, Feb 4, 2015 at 7:58 PM, Fu, Ju
i...@intel.com>
> > > > > wrote:
> > > > > > >
> > > > > > > > What are the test cases don't work for Crosswalk? I'd like to
> > do
> > > > > > whatever
> > > > > > > >
; > > > > > So, Crosswalk 10 (and, I believe, 11) work great for Cordova.
> There
> > > is
> > > > a
> > > > > > failing test in File Transfer, though, that appears to be a
> > threading
> > > > > issue
> > > &g
whatever
> >> > > > > I can to help.
> >> > > > >
> >> > > >
> >> > > > So, Crosswalk 10 (and, I believe, 11) work great for Cordova.
> There
> >> is
> >> > a
> >> > > > failing test i
ng test in File Transfer, though, that appears to be a
> threading
> > > > issue
> > > > > causing a NPE deep inside of OkHTTP.
> > > > >
> > > > > It's very similar to a bug we solved almost a year ago:
> > > > > htt
gt; > > > failing test in File Transfer, though, that appears to be a
>> threading
>> > > issue
>> > > > causing a NPE deep inside of OkHTTP.
>> > > >
>> > > > It's very similar to a bug we solved almost a yea
od, and while the last time, the cause was obvious
> > > > (connections opened on one thread, and closed on another), this time
> > > > everything *should* be happening on the same thread.
> > > >
> > > > I've just created https://issues.apache.org/jira/brow
; > everything *should* be happening on the same thread.
> > >
> > > I've just created https://issues.apache.org/jira/browse/CB-8431 if you
> > > want
> > > to take a look. I haven't had the chance to really dig into where the
> > error
> >
into where the
> error
> > is coming from yet, but I'll take a closer look tomorrow.
> >
> > Ian
> >
> >
> >
> > >
> > > -Original Message-
> > > From: agri...@google.com [mailto:agri...@google.com] On Behalf Of
> Andre
I'll take a closer look tomorrow.
>
> Ian
>
>
>
> >
> > -Original Message-----
> > From: agri...@google.com [mailto:agri...@google.com] On Behalf Of Andrew
> > Grieve
> > Sent: Thursday, February 05, 2015 3:43 AM
> > To: dev
> > Subject
ser look tomorrow.
Ian
>
> -Original Message-
> From: agri...@google.com [mailto:agri...@google.com] On Behalf Of Andrew
> Grieve
> Sent: Thursday, February 05, 2015 3:43 AM
> To: dev
> Subject: Re: [DISCUSS] Cordova-Android 4.0.0 Release
>
> On Wed, Feb 4, 2015 at
request a PR in here
> > https://github.com/MobileChromeApps/cordova-
> > crosswalk-engine/pull/17.
> >
> > Thanks,
> > Junwei.
> >
> > -Original Message-
> > From: agri...@google.com [mailto:agri...@google.com] On Behalf Of
> > Andrew
/github.com/MobileChromeApps/cordova-
> > crosswalk-engine/pull/17.
> >
> > Thanks,
> > Junwei.
> >
> > -Original Message-
> > From: agri...@google.com [mailto:agri...@google.com] On Behalf Of Andrew
> > Grieve
> > Sent: Wednesday, Februar
alk-11, and it was our plan to be released. I request a
> PR in here https://github.com/MobileChromeApps/cordova-
> crosswalk-engine/pull/17.
>
> Thanks,
> Junwei.
>
> -Original Message-
> From: agri...@google.com [mailto:agri...@google.com] On Behalf Of Andrew
>
...@google.com [mailto:agri...@google.com] On Behalf Of Andrew Grieve
Sent: Wednesday, February 04, 2015 3:53 AM
To: dev
Subject: Re: [DISCUSS] Cordova-Android 4.0.0 Release
And, of course, for your FileTransfer change :P
I just last night finished up the fixing of for
gradle-based builds, so we're cert
And, of course, for your FileTransfer change :P
I just last night finished up the fixing of for
gradle-based builds, so we're certainly nearing the finish line for 4.0.0
known issues.
Of the list from before, only remaining are:
- Ian's been working on getting crosswalk 10 working and is hittin
I just remembered that there should be a plugins release before
Android 4.0.0 goes out because of the moving of the splashscreen logic
out of the platform and into the plugin. As far as I can tell, that's
still unreleased.
-
To un
file system entry
>>> >> > > > root.getFile('../' + fileName, {
>>> >> > > > create : false
>>> >> > > > }, succeed.bind(null, done,
>>> >> > > > "root.getFile('../"+fileName+ "')- Unexpected su
t;> > > > failure
>> >> > > > • Expected null to be 401
>> >> > > > it('filetransfer.spec.6 should get 401 status on
>> >> http
>> >> > > > basic auth failure', function (done) {
>
uldn’t find a fire issue):
>>>> >> > > > • root.getFile succeeds, it is expected to fail.
>>>> >> > > > var fileName = "traverse.file.uri";
>>>> >> > > > // create a new f
basic_auth';
> >> > > >
> >> > > > var downloadFail = function (error) {
> >> > > > expect(error.http_status).toBe(401);
> >> > > > expect(error.http_status).not.
t;> > "Ensure "
>> > > > + fileURL + " is in the white list");
>> > > > done();
>> > > > };
>> > > >
>> > > > transfer.download(fileURL, localFilePath,
>> > > > unexpectedCallbacks.httpWin, downlo
gt; > > >
> > > > > transfer.download(fileURL, localFilePath,
> > > > > unexpectedCallbacks.httpWin, downloadFail);
> > > > > });
> > > > >
> > > > > org.apache.cordova.geolocation.te
gt; > > object", function (done) {
> > > > // this test asks for using geolocation and
> interrupts
> > > > autotests running.
> > > > // That's why we have to pending that for Windows
> Store
> > > >
t; - 6 failures in 4.0.4
> Ideally we should bring those numbers to 0 to ensure a stable release.
>
> -Original Message-
> From: Joe Bowser [mailto:bows...@gmail.com]
> Sent: Wednesday, January 28, 2015 10:45 AM
> To: dev@cordova.apache.org
> Subject: Re: [DISCUSS] Cordova
AM
To: dev@cordova.apache.org
Subject: Re: [DISCUSS] Cordova-Android 4.0.0 Release
On Wed Jan 28 2015 at 10:38:07 AM Andrew Grieve
wrote:
>
> - Make CordovaActivity not implement CordovaInterface, but instead
> provide CordovaInterface via an inner class (to solidify that you
> can
}
> > > navigator.geolocation.getCurrentPosition(function (p)
> {
> > > expect(p.coords).toBeDefined();
> > > expect(p.timestamp).toBeDefined();
> > > done();
> > >
);
> > },
> > fail.bind(null, done),
> > {
> > maximumAge: 30 // 5 minutes maximum age of cached
> > position
> > });
> > });
> >
> > org.apache.cor
> • Expected true to be false
> it("geolocation.spec.8 should be called with a Position
> object", function (done) {
> // this test asks for using geolocation and interrupts
> autotests running.
> // That's wh
expect(p.timestamp).toBeDefined();
done();
},
fail.bind(null, done),
{
maximumAge: (5 * 60 * 1000) // 5 minutes maximum age of
cached position
});
Joe and team,
I work for Ionic and I've had some involvement with the Cordova project
since last year. At Ionic, we've released a Crosswalk build using Cordova
Android 4.0 so we can use the cordova crosswalk engine for the ionic
platform.
I've been working with Ian and Andrew on this to gather mo
Hey
So, it's finally here. I want to see us work more on Pluggable Webviews,
and adding the API, but I think it's time that we released what we've been
working on for almost a year to our users. I know that the API isn't
exactly the most awesome we can make it, but it works, and I'd rather have
66 matches
Mail list logo