Return-Path: 
 <dev-return-23037-apmail-cordova-dev-archive=cordova.apache.org@cordova.apache.org>
X-Original-To: apmail-cordova-dev-archive@www.apache.org
Delivered-To: apmail-cordova-dev-archive@www.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id F2F36F4A9
	for <apmail-cordova-dev-archive@www.apache.org>;
 Mon, 13 May 2013 21:22:47 +0000 (UTC)
Received: (qmail 68557 invoked by uid 500); 13 May 2013 21:22:47 -0000
Delivered-To: apmail-cordova-dev-archive@cordova.apache.org
Received: (qmail 68522 invoked by uid 500); 13 May 2013 21:22:47 -0000
Mailing-List: contact dev-help@cordova.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:dev-help@cordova.apache.org>
List-Unsubscribe: <mailto:dev-unsubscribe@cordova.apache.org>
List-Post: <mailto:dev@cordova.apache.org>
List-Id: <dev.cordova.apache.org>
Reply-To: dev@cordova.apache.org
Delivered-To: mailing list dev@cordova.apache.org
Received: (qmail 68514 invoked by uid 99); 13 May 2013 21:22:47 -0000
Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230)
    by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 13 May 2013 21:22:47 +0000
X-ASF-Spam-Status: No, hits=-0.7 required=5.0
	tests=RCVD_IN_DNSWL_LOW,SPF_PASS
X-Spam-Check-By: apache.org
Received-SPF: pass (nike.apache.org: domain of bowserj@gmail.com designates
 209.85.212.43 as permitted sender)
Received: from [209.85.212.43] (HELO mail-vb0-f43.google.com) (209.85.212.43)
    by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 13 May 2013 21:22:41 +0000
Received: by mail-vb0-f43.google.com with SMTP id p14so5678012vbm.30
        for <dev@cordova.apache.org>; Mon, 13 May 2013 14:22:20 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20120113;
        h=mime-version:x-received:date:message-id:subject:from:to
         :content-type;
        bh=gvNObQf4N53Mmo1KgbBRRJvwudH+GTDpdFR6X9mW9U4=;
        b=NNi2k+PXMMTQXoWiBs4ja07cSP0V398/8xkjPDKkmLaAz4kb9eWAiv4kh03IXFofhg
         FTJTxnRvhQ4Ug0HfscCRVwIahDMZunFl7zO6l+2A1HOocNli/KgStpspXWN38nomy4in
         plGBwVWvfdwb3ET5fShiBpame7tu3gRoQ0AXFNumCbvj3frc20RpCidBGBDUmqBoQ6rO
         mu6ig5uj6LNX/ij9HnoCvwbKfZD4pAgAd/pBacQJe/xF4KS5EwxvU6iyZPGaBQiILtS7
         GhiN6PAGIGmsxXO6ftDkKrv2Pa9CRIBNT6M18ObKvAYqJ1W1+GVxuZ2qrFI6HA3DUEKG
         f36A==
MIME-Version: 1.0
X-Received: by 10.52.29.172 with SMTP id l12mr16853294vdh.47.1368480140670;
 Mon, 13 May 2013 14:22:20 -0700 (PDT)
Received: by 10.221.8.196 with HTTP; Mon, 13 May 2013 14:22:20 -0700 (PDT)
Date: Mon, 13 May 2013 14:22:20 -0700
Message-ID: 
 <CAOBL_k4GTi4ZNji6_rAo8yCsHpxeucW_kZqDWNjzeyo-GnTa0w@mail.gmail.com>
Subject: [Android] Deprecate HTC 2.3 Android console.log support in 3.0
From: Joe Bowser <bowserj@gmail.com>
To: dev <dev@cordova.apache.org>
Content-Type: text/plain; charset=ISO-8859-1
X-Virus-Checked: Checked by ClamAV on apache.org

Hey

There's a known bug in HTC's WebView that suppressed console.log on
old Gingerbread devices.  This is only on devices that run HTC Sense,
and not devices like the Nexus One.  How do people feel about
deprecating console.log in 3.0.  I know that Simon hated this
particular chunk of code, and wanted to toss it by the wayside a while
ago.

It says it was supposed to be ripped out this release, but I don't see
it on the wiki, so I'm giving it until 3.0 to be removed.  Does that
sound reasonable?

Joe