The issue looks to be that the <div> tag is being defined with an =E2=80=9C=
on=E2=80=9D method
[Object, HTMLDivElement]
[+] on function()

Object, (Function)
=20
The icefaces-compat.js script blows up on line #5063
if(eventName.include(":")){
=20
=20

It looks like there is a conflict between Prototype code (included in icefa=
ces-compat.js) and ESRI code when defining Element.on function. ESRI code i=
s calling the Element.on function with a different set of parameters than w=
hat the function expect. As you can see in the screenshot the call stack sh=
ows clearly how the second parameter is a function while the Prototype's El=
ement.on function definition expects a string that represent the event type=
(such as 'onclick').

Further details from the customer indicate that The ESRI ArcGIS v2.8 product does work with ICEfaces, but their attempt to use the ArcGIS v3.2 release fails with an apparent JS conflict, potentially between ICEfaces and the Dojo library used by ArcGIS.

Need to analyze the nature of the conflict when using ArcGIS 3.2 and ICEfaces 3.2.

My previous analysis stands as correct. Both in ICEfaces3 and ICEfaces1.8 the Prototype library is attaching the "on" method to the elements that it wraps. A method with the same name is registered by ESRI but it is overritten by Prototype, causing ESRI to fail when invoking the wrong method implementation.

Attach patch for ICEFaces 1.8 code that renames the on method to prototype_on to avoid the name conflict.

Renamed 'on' method wired (by Prototype lib) to DOM nodes to "prototype_on" to avoid conflict with AEGIS library.
Applied fix to ICEfaces 1.8 trunk and ICEfaces3 trunk.