I solved this problem just a few weeks ago myself :) It is a very bad bug that is very hard to track down, the only error is "submit is not a function".
The solution is to assign an id to your submit button, like this: <t:submit id="saveButton"/>. You should always do that anyway, it makes code clearer and it is easier to test with tools like selenium. On Wed, Dec 9, 2009 at 1:33 AM, Vangel V. Ajanovski <a...@ii.edu.mk> wrote: > Sorry, but there might be some problem with the mailing list, my message > was considered as a SPAM and first the text was removed from the > message, and the next time I got info that it was considered as SPAM. > > I am sending the message again. > > On 08.12.2009 02:47, Mite wrote: > > I have written this code so far: > > > > <form t:type="form"> > > <t:selectObject t:id="courses" list="courses" value="currentCourse" > > labelField="literal:courseId" onChange="form.submit();"/> > > <t:submit/> > > </form> > > > > This issue is not really a problem of Tapestry, this is a Javascript > browser implementation problem. > In my code sample this works in IE 8, and it does not work in Firefox > 3.6 or Opera 10 > > Take the submit button out, and it will work with no problem. > > So, What exactly happens in for example Firefox is that when you add a > Submit button, the Submit() function is overriden with the Submit button > and it becomes a property. > Now the form.submit is not the function for submitting any more, but in > fact now it is the submit button itself. > > I think that I never ever had a need to use a button and a list for > submitting at the same time, so I never saw this as a problem. > > But, the bad thing is that here Thiago's solution does not help - with > it I get an > Event.observe is not a function > And now it does not work even in IE. > >
