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 brian.leroux@gmail.com
 designates 209.85.223.179 as permitted sender)
MIME-Version: 1.0
Sender: brian.leroux@gmail.com
In-Reply-To: 
 <CADVgkyNBq20Yx2QDeCw1crmDDxG87OUiGbLj99nGQdwpZXLYug@mail.gmail.com>
References: <CE05A0CF.22532%fil@adobe.com>
	<CADVgkyNBq20Yx2QDeCw1crmDDxG87OUiGbLj99nGQdwpZXLYug@mail.gmail.com>
Date: Fri, 12 Jul 2013 12:19:31 -0700
Message-ID: 
 <CADVgkyMGtSX+5bd3ba+ppyBNMARSMPEwNGETZ7ZNv9WSSgaFMA@mail.gmail.com>
Subject: Re: [JS] Channel to be compatible with EventListener?
From: Brian LeRoux <b@brian.io>
To: dev@cordova.apache.org
Content-Type: text/plain; charset=ISO-8859-1

I rescind my last comment. Given http://issues.cordova.io/3786 it
looks like he wants compat at the event object on our custom events
which makes sense. We should have this level of compatibility on our
event code!


On Fri, Jul 12, 2013 at 12:14 PM, Brian LeRoux <b@brian.io> wrote:
> Given the only reason is compatibility w/ the DOM spec, which this has
> little to nothing to do with, I see no reason why we would add that
> code.
>
> On Fri, Jul 12, 2013 at 12:02 PM, Filip Maj <fil@adobe.com> wrote:
>> See https://issues.apache.org/jira/browse/CB-3785
>>
>> Thoughts?
>>