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

RE: Actions in form controls

From: John Boyer <JBoyer@PureEdge.com>
Date: Thu, 12 Feb 2004 15:41:39 -0800
Message-ID: <7874BFCCD289A645B5CE3935769F0B528B5D70@tigger.pureedge.com>
To: "Mark Birbeck" <mark.birbeck@x-port.net>, "Borgrink, Susan" <sborgrink@progeny.net>, "Jonathan Ito" <jito@ksventures.com>
Cc: <www-forms@w3.org>

The detail I think he missed is the namespace on the event attribute.

John Boyer, Ph.D.
Senior Product Architect and Research Scientist
PureEdge Solutions Inc.

-----Original Message-----
From: Mark Birbeck [mailto:mark.birbeck@x-port.net]
Sent: Thursday, February 12, 2004 3:23 PM
To: 'Borgrink, Susan'; 'Jonathan Ito'
Cc: www-forms@w3.org
Subject: RE: Actions in form controls

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:label>Item 1</xforms:label>
			<xforms:label>Item 2</xforms:label>
			<xforms:action ev:event="xforms-select">
				<xforms:send submission="debug" />

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.



Mark Birbeck

Received on Thursday, 12 February 2004 18:41:53 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:36:11 UTC