- From: John Boyer <boyerj@ca.ibm.com>
- Date: Wed, 8 Oct 2008 13:55:43 -0700
- To: www-html-editor@w3.org
- Cc: www-html@w3.org, public-forms@w3.org
- Message-ID: <OFB691BFB2.EDD5DC67-ON882574DC.00703513-882574DC.0072F712@ca.ibm.com>
On the Forms WG telecon today, Steven recommended it would be OK to submit
the following as a last call comment (despite the late date).
XML Events 2 has an event() function, and it depends on the consuming
language profile to provide specific context information properties that
can be returned by the function.
However, there are at least five properties that XML Events 2 could offer
to all consuming languages:
event('name') - the name of the event, e.g. xforms-insert (this is more
for completeness, since often you will know this based on ev:event)
event('targetid') - returns ID of the event target
event('phase') - returns capture or bubble, depending on the phase the
event is in when the event() function is invoked.
event('bubbles') - returns true or false depending on whether or not the
event bubbles
event('cancelable') - returns true or false depending on whether the
event propagation can be stopped.
I can't recall offhand whether the ability to stop the default action is
also part of cancelable, but it should be accounted for as well.
The most important ones, in my view, seem to be targetid and phase. I
have hit a few cases at least where I want to do something *if* the event
is going to a particular element or *if* it is in the capture phase.
Best regards,
John M. Boyer, Ph.D.
STSM, Interactive Documents and Web 2.0 Applications
Chair, W3C Forms Working Group
Workplace, Portal and Collaboration Software
IBM Victoria Software Lab
E-Mail: boyerj@ca.ibm.com
Blog: http://www.ibm.com/developerworks/blogs/page/JohnBoyer
Blog RSS feed:
http://www.ibm.com/developerworks/blogs/rss/JohnBoyer?flavor=rssdw
Received on Wednesday, 8 October 2008 20:56:44 UTC