Mailing-List: contact dev-help@cordova.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cordova.apache.org
Received-SPF: pass (nike.apache.org: domain of mmocny@google.com designates
 209.85.220.174 as permitted sender)
MIME-Version: 1.0
Sender: mmocny@google.com
In-Reply-To: 
 <CAOBL_k5-cJW2tbmVFAKQbS5UY_xWoVwYmt4J7tFhDO-iR6m6nQ@mail.gmail.com>
References: 
 <CAOBL_k5-cJW2tbmVFAKQbS5UY_xWoVwYmt4J7tFhDO-iR6m6nQ@mail.gmail.com>
From: Michal Mocny <mmocny@chromium.org>
Date: Mon, 8 Dec 2014 10:52:32 -0500
Message-ID: 
 <CAEeF2Tcj=HSogWo4HwGVmO8BnOMw6DtH0vXy4-V1CDOH2aF88A@mail.gmail.com>
Subject: Re: 4.0 Sprint Tasks (Another "Hey, let's ship 4.0.x soon" post)
To: dev <dev@cordova.apache.org>
Content-Type: multipart/alternative; boundary=bcaec52d598d57929a0509b66bfc

--bcaec52d598d57929a0509b66bfc
Content-Type: text/plain; charset=UTF-8

On Sun, Dec 7, 2014 at 11:53 PM, Joe Bowser <bowserj@gmail.com> wrote:

> Hey
>
> After messing with the JS for a week, I decided for now to stop work on
> MozillaView.  I think I've managed to prove that the concept is at least
> possible, but I really feel that it's still too unstable to actually show
> past a demo/POC at this time.  We've definitely learned some lessons, and
> I'll probably write a blog post on them soon, and pick up work in the new
> year.
>
> That said, we should really concentrate on shipping 4.0 in January, we
> should do the following:
>
> 1. Bump up the targeted version to 5.0
>
Yes, please.


> 2. Allow for users to target KitKat for Quirks Mode (I'm not kidding,
> Quirks mode is back.  Chrome is the new IE! WTF MAN!)
>

Quirks mode is for targetSdk 18 or lower running on KitKat (19) or newer
devices.  This is because the default WebView changed dramatically from
18->19 and Android tries to have a good compatibility story.  Not sure
whats so WTF about that?

Anyway, are you suggesting that we need to support enabling quirks mode
even with targetSdk 19+ (as has been the cordova-android default for a
while now, anyway)?


> 3. Get the gradle work in.  MUCH FASTER! LESS SPAM! WOW!
>

Do we want to add this next year in 4.0 or ship this year in 3.7 (behind a
flag, maybe)?


> 4. Get the JUnit tests working with Gradle/Android Studio.  I don't think
> this is a 4.0 task per-se, but we should do it right after 4.0 is released.
> 5. Stare at the pie chart wishing that 9 was 5.  (Anyone who knows our
> deprecation policies knows EXACTLY what I'm talking about).
>
> I do have one API change I want to make.  I want to rename the
> CordovaWebView interface CordovaWebInterface so that it's obvious that it's
> an interface.  Since people using the old CordovaWebView embedded feature
> are going to have to do a find/replace on the XML, this doesn't really
> matter.  Of course, the people using this feature may beg to differ.  If
> you're using this feature, and you care about it still working with your
> current code, PLEASE TEST 4.0 NOW.
>
> Thoughts?
>
> Joe
>

--bcaec52d598d57929a0509b66bfc--