Fix for: ENYO-56

# Issue

When using the delegate support for forward events from declarative child-components to an owner handler, directly, it is being lost from repeater children. This happens because children of repeater children are scoped to be owned by the repeater child for scoping related issues for a repeated child. This does, however, keep the expected behavior of delegated events from working.

# Fix

We can clearly identify when those cases exist and we can attempt to forward them to the owner of the repeater child (expected behavior) when possible.
I noticed that too but matched it with the behavior that is already in place so it would be consistent. 

Sent from my iPhone

> On Oct 9, 2014, at 6:14 PM, Ryan Duffy <notifications@github.com> wrote:
> 
> In source/ui/data/RepeaterChildSupport.js:
> 
> > +				var owner;
> > +				
> > +				// if the event is coming from a child of the repeater-child (this...) and has a
> > +				// delegate assigned to it there is a distinct possibility it is supposed to be
> > +				// targeting the instanceOwner of repeater-child not the repeater-child itself
> > +				// so we have to check this case and treat is as expected - if there is a handler
> > +				// and it returns true then we must skip the normal flow
> > +				if (event.originator !== this && event.delegate && event.delegate !== this) {
> > +					if (typeof this[name] != 'function') {
> > +						// ok we don't have the handler here let's see if our owner does
> > +						owner = this.getInstanceOwner();
> > +						if (owner && owner !== this) {
> > +							if (typeof owner[name] == 'function') {
> > +								// alright it appears that we're supposed to forward this the next
> > +								// owner instead
> > +								return owner.dispatch(name, event, sender);
> I think we need to return true here regardless because we're short-circuiting the usual event bubbling chain. Otherwise, it's possible (albeit remote) for an upstream handler to be called twice. See the attached App.js in JIRA for an example.
> 
> —
> Reply to this email directly or view it on GitHub.