W3C home > Mailing lists > Public > public-xhtml2@w3.org > October 2008

LC Comment: Common event info from event() (PR#8056)

From: <boyerj@ca.ibm.com>
Date: Wed, 8 Oct 2008 16:02:24 -0500
Message-Id: <200810082102.m98L2OLS007809@htmlwg.mn.aptest.com>
To: public-xhtml2@w3.org
CC: xhtml2-issues@mn.aptest.com


This is a multipart message in MIME format.
--=_alternative 0072F6AE882574DC_=
Content-Type: text/plain; charset="US-ASCII"

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


--=_alternative 0072F6AE882574DC_=
Content-Type: text/html; charset="US-ASCII"


<br><font size=2 face="sans-serif">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).</font>
<br>
<br><font size=2 face="sans-serif">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.</font>
<br>
<br><font size=2 face="sans-serif">However, there are at least five properties
that XML Events 2 could offer to all consuming languages:</font>
<br>
<br><font size=2 face="sans-serif">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)</font>
<br>
<br><font size=2 face="sans-serif">event('targetid') - returns ID of the
event target</font>
<br>
<br><font size=2 face="sans-serif">event('phase') - returns capture or
bubble, depending on the phase the event is in when the event() function
is invoked.</font>
<br>
<br><font size=2 face="sans-serif">event('bubbles') - returns true or false
depending on whether or not the event bubbles</font>
<br>
<br><font size=2 face="sans-serif">event('cancelable') - returns true or
false depending on whether &nbsp;the event propagation can be stopped.
</font>
<br>
<br><font size=2 face="sans-serif">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.</font>
<br>
<br><font size=2 face="sans-serif">The most important ones, in my view,
seem to be targetid and phase. &nbsp;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.</font>
<br>
<br><font size=2 face="sans-serif">Best regards,</font>
<br><font size=2 face="sans-serif">John M. Boyer, Ph.D.<br>
STSM, Interactive Documents and Web 2.0 Applications<br>
Chair, W3C Forms Working Group<br>
Workplace, Portal and Collaboration Software<br>
IBM Victoria Software Lab<br>
E-Mail: boyerj@ca.ibm.com &nbsp;<br>
<br>
Blog: </font><a href=http://www.ibm.com/developerworks/blogs/page/JohnBoyer><font size=2 face="sans-serif">http://www.ibm.com/developerworks/blogs/page/JohnBoyer</font></a><font size=2 face="sans-serif"><br>
Blog RSS feed: </font><a href="http://www.ibm.com/developerworks/blogs/rss/JohnBoyer?flavor=rssdw"><font size=2 face="sans-serif">http://www.ibm.com/developerworks/blogs/rss/JohnBoyer?flavor=rssdw</font></a><font size=2 face="sans-serif"><br>
<br>
</font>
--=_alternative 0072F6AE882574DC_=--
Received on Wednesday, 8 October 2008 21:03:42 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 23 February 2010 18:12:50 GMT