Yeah, sometimes quick fixes, well, aren't!
But cool. As you're using Zones I'll mention another trick...
If you put the event handler on the document, or some parent element
that doesn't get updated, then you don't have to re-apply the event
handler on every zone / ajax update.
e.g. the following will submit the form on all select change events
and you only ever need to call jsSupport.require() once when the page
loads:
define ["t5/core/dom"], (t5) ->
return ->
t5.onDocument "change", "select", (e) ->
form = this.findParent("form")
form.trigger "submit"
Steve.
On 11 March 2013 09:06, Bob Harner <bobhar...@gmail.com> wrote:
> Steve,
>
> Yeah, I hadn't gotten around to switching this code to unobtrusive
> JavaScript yet and was hoping for a quick substitute.
>
> Your code did the trick, it works perfectly.
>
> Of course, I'll still need to adjust the module to set up a additional
> event handlers for other events, but I guess I can figure that out
> (i.e. Initialize#invoke(String)) now that you've given me a good
> start.
>
> Thanks!
>
> On Sun, Mar 10, 2013 at 8:28 PM, Steve Eynon
> <steve.ey...@alienfactory.co.uk> wrote:
>> Oh, I see - you have inline javascript in the onchange handler. I
>> don't think that's going to work - you need to wrap the element in T5s
>> core DOM which is defined by RequireJS:
>>
>> http://people.apache.org/~hlship/t5api/coffeescript/t5-core-dom-prototype.html
>>
>> Do this instead:
>>
>> /META-INF/modules/formSubmitter.js
>>
>> define(["t5/core/dom"], function(t5) {
>> return function(selectClientId) {
>> return t5(selectClientId).on('change', function(e) {
>> var form = this.findParent("form");
>> return form.trigger("submit");
>> });
>> };
>> });
>>
>> Or use CoffeeScript:
>>
>> /META-INF/modules/formSubmitter.coffee
>>
>> define ["t5/core/dom"], (t5) ->
>> return (selectClientId) ->
>> t5(selectClientId).on 'change', (e) ->
>> form = this.findParent("form")
>> form.trigger "submit"
>>
>> Then in a render phase method in your component / page:
>>
>> jsSupport.require("formSubmitter").with(select.getClientId());
>>
>> Steve.
>>
>>
>> On 11 March 2013 02:32, Lenny Primak <lpri...@hope.nyc.ny.us> wrote:
>>> In 5.3, you had to do setSubmittingElement(). Not sure if this applies
>>> still in 5.4, but if it does,
>>> it will need to be called.
>>>
>>> On Mar 10, 2013, at 1:39 PM, Lance Java wrote:
>>>
>>>> You need to fire the "click" event on the submit button, not "submit".
>>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
>> For additional commands, e-mail: users-h...@tapestry.apache.org
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
> For additional commands, e-mail: users-h...@tapestry.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
