[TAP5-2077] ElementWrapper#onevent jQuery implementation can return a wrong ElementWrapper

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Duplicate
• Affects Version/s: 5.4
• Component/s: tapestry-core
• Labels: dom javascript jquery patch
• Assignee: Unassigned
• Reporter: Julien Blatecky
• Created: 05/Mar/13 14:59
• Updated: 15/Mar/13 10:29
• Resolved: 15/Mar/13 10:29

Description

Considers we bind an event on an element (<a> for example) and this element contains some other element (<span> for instance).
The event that will be triggered returns an ElementWrapper wrapping the span element if we clicked on span, instead of returning a wrapped element of the <a> element.

Consequently, in the case of a a[data-update-zone] containing some span or img elements, clicking on one of these elements raises a javascript error : "Attempt to wrap a null DOM element" when handling the callback.

Indeed, in the wrapped callback (line 95 in the coffeescript jquery dom) the ElementWrapper is instantiated with the "event.target" returned by jquery, which is not the element on which we defined the event, but the deeper element on which the event occurs. jQuery.com says "The target property can be the element that registered for the event or a descendant of it.", whereas "this" will be "the current DOM element within the event bubbling phase." just like "event.currentTarget".

Issue Links

• is a clone of: TAP5-2060 5.4-alpha-2 - Markup in eventlink body prevents ajax
• relates to: TAP5-2060 5.4-alpha-2 - Markup in eventlink body prevents ajax