There is a malformedXML error from the bridge after submitting the show delay change. See screenshot-1.png.

Validation shows that the response is valid XML. See screenshot-2.png. The JS is also valid as inspected by IntelliJ.

[12:04:27 PM] Ken Fyten: Yip, try removing the singleSubmit tag usage and replacing with f:ajax to see if it changes anything.

Same. See screenshot-3.png.

When the updates come back, one of the updates is a single <script> element, responsible for updating the tooltip to use the newly selected attribute values:

<update id="j_idt68:tooltip">
<![CDATA[<script id="j_idt68:tooltip" type="text/javascript">jQuery(function() {widget_j_idt68_tooltip = new ice.ace.Tooltip({"global":false,"id":"j_idt68:tooltip","displayListener":false,"forComponent":"j_idt68:text",content:document.getElementById('j_idt68:tooltip_content').innerHTML,"show":{"when":

,"delay":1000,"effect":{"length":0,"type":"grow"}},"hide":{"when":

,"delay":0,"effect":{"length":0,"type":"grow"}},"position":{"container":jQuery(ice.ace.escapeClientId('j_idt68:text')).parent(),"corner":

}});});</script>]]>
</update>

It appears that, in processing this script, JSF runs into difficulty - this affects both Mojarra and MyFaces it appears although there isn't an error with MyFaces.

I looked at the TooltipRenderer and specifically at a recent fix related to http://jira.icefaces.org/browse/ICE-7588. As part of that fix, it added an id to the script:

protected void encodeScript(FacesContext facesContext, Tooltip tooltip) throws IOException {
ResponseWriter writer = facesContext.getResponseWriter();
boolean global = tooltip.isGlobal();
String owner = getTarget(facesContext, tooltip);
String clientId = tooltip.getClientId(facesContext);

writer.startElement("script", null);
-> writer.writeAttribute("id", clientId, null);
writer.writeAttribute("type", "text/javascript", null);

Simply by commenting out that single line, the tooltip example in the showcase works again and the attributes are properly applied. The downside is that the updates are much bigger as they have to go higher up the chain in order to find a common parent to replace.

Had a quick chat with Mircea and he confirmed some things I was suspecting. While adding and id to the script may help with the issue for ICE-7588, we generally recommend the practice of putting a containter, such as a <span> tag, around the script element and add the id to the container element. However, I tried that technique in the TooltipRenderer and the problem was still there where the attributes are not being applied properly. However the error is gone and debugging shows that the scripts are being added and removed from the head.

I've applied the fix that puts a containing <span> around the script so that when Mojarra sees the update as a single script, it doesn't complain. After that it appeared that everything was doing what it was supposed to but the tooltip attributes were still not appearing to be applied.

As it eventually turns out, they scripts with the updates are being received and applied but they are not being removed. That is, all the choices are being applied and remembered. I was only able to determine this by noting that, as I changed more attributes, the tooltip display got more flickery and flakey.

To finally verify, I:

• set all the delays to their longest setting (2 seconds)
• navigated to a different demo (e.g. tabset) then navigated back
• check to ensure that the current settings are working (everything should take 2 seconds)
• then change only the effect (e.g. from Slide to Fade)
• try the tooltip again

As you do this, you should note that the image both fades AND slides in. In other words, both effects are in play. The same applies for the delay values which is what causes the flakey behaviour and the appearance that the attributes are not being applied.

I presume that the tooltip.js file needs to be modified so that the various listeners are removed and re-applied when the updates come in.

Two causes:
1. App. backing bean didn't initialize values to match dropdown lists, resulting in zeros and empty strings for the effects and position params. See screenshot-4.png.
2. Same general problem as ICE-7361 and ICE-7388 and ICE-7506: multiple instances and framework trying to control the same sections of HTML and CSS. See screenshot-5.png.

Modified: C:\svn\ossrepo\icefaces3\trunk\icefaces\ace\component\resources\icefaces.ace\tooltip\tooltip.js
Modified: C:\svn\ossrepo\icefaces3\trunk\icefaces\samples\showcase\showcase\src\main\java\org\icefaces\samples\showcase\example\ace\tooltip\TooltipOverviewBean.java
Completed: At revision: 27068

ICE-7601: add a containing span around the script so that Mojarra doesn't complain during update processing.
Caused regression of ICE-7588.