W3C home > Mailing lists > Public > www-forms@w3.org > February 2004

RE: Actions in form controls

From: Mark Birbeck <mark.birbeck@x-port.net>
Date: Thu, 12 Feb 2004 23:23:20 -0000
To: "'Borgrink, Susan'" <sborgrink@progeny.net>, "'Jonathan Ito'" <jito@ksventures.com>
Cc: <www-forms@w3.org>
Message-ID: <002901c3f1bf$3411dfa0$0d01a8c0@W100>

Hi Susan,

> Have you tried changing the <action event="xforms-value-changed">
> to <action event="xforms-select">?  "xforms-select" is the
> notification sent out when a select1 or select is selected ... 

'xforms-select' is targeted at the xf:item selected, not the xf:select1.
For example:

	<xforms:select1 ref="myValue">
		<xforms:label>Choose one</xforms:label>
		<xforms:item>
			<xforms:label>Item 1</xforms:label>
			<xforms:value>v1</xforms:value>
		</xforms:item>
		<xforms:item>
			<xforms:label>Item 2</xforms:label>
			<xforms:value>v2</xforms:value>
			<xforms:action ev:event="xforms-select">
				<xforms:send submission="debug" />
			</xforms:action>
		</xforms:item>
	</xforms:select1>

This would only do the submission if "Item 2" was selected, but not if
"Item 1" was selected. ('xforms-select' would also go to an xf:case, in
an xf:switch.)


> ... not "xforms-value-changed".

'xforms-value-changed' is sent to *any* control that it bound to
instance data that has changed, so Jonathan's example is correct.
Assuming that his markup is correct (no missing prefixes, etc.), then he
just needs to check that the implementation he is using supports it.

Regards,

Mark


Mark Birbeck
CEO and CTO
x-port.net

http://www.formsPlayer.com/
Received on Thursday, 12 February 2004 18:23:28 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Saturday, 10 March 2012 06:21:57 GMT