You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by ta...@jakarta.apache.org on 2004/08/27 16:18:27 UTC

[Jakarta Tapestry Wiki] New: ClientSideEventSupportProposal

   Date: 2004-08-27T07:18:27
   Editor: HowardLewisShip <hl...@apache.org>
   Wiki: Jakarta Tapestry Wiki
   Page: ClientSideEventSupportProposal
   URL: http://wiki.apache.org/jakarta-tapestry/ClientSideEventSupportProposal

   no comment

New Page:

As people have done more work with client-side scripting in Tapestry 3.0 some issues have come up.

Basically ... all form.onsubmit event handlers are not equal.

Sometimes you are cancelling a form, in which case no event handlers should be triggered on the client.

Sometimes you are refreshing a form (a standard example is submitting a form when a drop down list changes, to update the options in a secondary, dependent drop down list). In this case, input validations should be skipped, but certain other onsubmit events should still occur (such as how the Palette component selects all in its selected list).

I prototyped a very simple JavaScript library that manages the list of event handlers on the client side, rather than trying to figure it all out on the server side. This needs to be augemented to support these differnt "qualities" or "priorities" of event handlers, and to integrate into the FormCancelProposal.

---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-dev-help@jakarta.apache.org