This occurs with several ICEmobile components:
When jsf.ajax.response is invoked, it converts sourceid into
an element:
// ensure context source is the dom element and not the ID
// per 14.4.1 of the 2.0 specification. We're doing it here
// before any errors or events are propagated becasue the
// DOM element may be removed after the update has been processed.
if (typeof context.sourceid === 'string')
{
context.sourceid = document.getElementById(context.sourceid);
}
Then the page is updated by JSF.
Then the ICEfaces bridge tries to walk up the ancestors to
determine if the source was an ICEfaces component (to know
whether to invoke our event listeners). In some
cases, the page update will stomp on the source element itself,
disconnecting it from the browser DOM. This causes the ancestor
ascend to bail out too early.
Bug
Major
MODIFY
/icefaces3/trunk/icefaces/core/src/main/javascript/application.js
This occurs with several ICEmobile components:
{ context.sourceid = document.getElementById(context.sourceid); }When jsf.ajax.response is invoked, it converts sourceid into
an element:
// ensure context source is the dom element and not the ID
// per 14.4.1 of the 2.0 specification. We're doing it here
// before any errors or events are propagated becasue the
// DOM element may be removed after the update has been processed.
if (typeof context.sourceid === 'string')
Then the page is updated by JSF.
Then the ICEfaces bridge tries to walk up the ancestors to
determine if the source was an ICEfaces component (to know
whether to invoke our event listeners). In some
cases, the page update will stomp on the source element itself,
disconnecting it from the browser DOM. This causes the ancestor
ascend to bail out too early.