XPage: Client Side Script Problem: Is it fixed in July Update?

HCL Domino Domino Forum
1

A bug has been documented that client-side JavaScript does not execute in buttons after a Partial Update (http://www-10.lotus.com/ldd/nd85forum.nsf/5f27803bba85d8e285256bf10054620d/e63e2f01382e1539852575a700370e75?OpenDocument)

Can anyone confirm whether or not this is really fixed in the update scheduled for July?

2

Subject: fix really needed

Hello all,I do agree with Russel. We need this problem fixed asap. We opened a ticket about it, but got no real feedback…

it really has to be fixed.

In the meanwhile, we use the following (painful) workaround :

<xp:link id=“btnEditSave” styleClass=“button”>

<xp:label value="Enregistrer" />

</xp:link>

<xp:button id="btnEditSaveTrigger" value="Enregistrer">

	<xp:eventHandler event="onclick" submit="true" refreshMode="complete">

		<xp:this.action>

			<xp:executeScript>

				<xp:this.script><![CDATA[#{javascript:

					// SERVER SIDE SCRIPTING HERE

				}]]></xp:this.script>

			</xp:executeScript>

		</xp:this.action>

	</xp:eventHandler>

</xp:button>

<xp:scriptBlock id="btnEditSaveAssociate">

	<xp:this.value><![CDATA[

		dojo.byId("#{id:btnEditSave}").onclick = function() {

			// CLIENT SIDE SCRIPTING HERE

		};

		dojo.byId("#{id:btnEditSaveTrigger}").click();

	]]></xp:this.value>

</xp:scriptBlock>

we add a onclick event handler on our button (which is a link for css needs).

This functions first executes client side code, and then clicks a hidden xpage button to trigger serverside code.

A pain to use, but it s only a workaround.

Please IBM fix this asap.

Luc

3

Subject: Fixed in the first 8.5.1 managed beta

Yes, the issue #PHAN7RKDER is fixed in the first 8.5.1 managed beta.It is fixed in builds with date stamps 20090510 or later.

4

Subject: Thank you for the update…

…it is helpful to know.

Thanks again.