The context menu calls the following function (note, this function is
called called from a simple "ul ... li" style of top menu, and the
same behavior is observed there):
function saveChanges(t, leaveScreen) {
$('form').trigger('submit');
if( leaveScreen ) {
exitScreen();
}
}
When the trigger fires, this function is called:
$('form').submit(function() {
clearEmptyRows();
$('tr.deleted td:first-child input').each(function() {
if( !$(this).hasClass('KeyField') ) return;
$('form').append('<input type="hidden" value="' +
this.value + '"
name="deleted"/>');
});
return true;
});
I've set a breakpoint in Firebug at the "return true" line, and it
does stop there. I've also set a breakpoint in the previous function
at the "if( leaveScreen ) {" line. It stops at that breakpoint too.
So I know these 2 functions are getting called. However, I expected
the data to be updated in the database, before calling exitScreen().
This does not appear to be the case. It looks like what's happening
is the chain of submit functions is stopping at the end of my submit
function. So the browser submit function never fires, which means the
data is never transmitted to the server. My Tomcat log does not show
data getting received by the server, so again, it looks like the
browser submit function fires.
On Jan 2, 12:15 pm, Joe <joseph.is...@gmail.com> wrote:
> What is the code for the context menu? I have a hunch it is somewhere
> in there.
>
> Joe
>
> On Jan 2, 11:17 am, TimW66 <timwilso...@gmail.com> wrote:
>
> > Thanks for the response. I changed the name attribute to be "save",
> > but that didn't work either. I think what's happening is there are
> > other event handlers getting executed in the for loop, and one of
> > those is returning a value that val gets set to, such that it doesn't
> > propagate to the next function; which in my case is the browser
> > submit. Of course, I have no idea which event handler is returning a
> > value that is causing val to get set that way.
>
> > On Jan 2, 10:21 am, Dave Methvin <dave.meth...@gmail.com> wrote:
>
> > > I have a suspicion...give the button a name other than submit.
>
> > >http://jibbering.com/faq/names/
