Debugging forms

[Michael Prescott <mi...@gmail.com>]

I have a form that involves a loop, and each row has some <t:submit>
buttons.  On Chrome, these buttons work just fine (triggering a server-side
event); in Firefox 4, the form submits, but the submit button's event isn't
triggered.

What techniques are available for debugging this?  I've got the
tapestry.events log channel output, which is why I can tell the submit
button's event handler isn't being triggered, but I'd like to get a bit
higher up the 'stack'.

Unfortunately, the POST data is incomprehensible, since everything's encoded
and it seems full of spurious differences (like encoded, transient IDs).

Any tips would be appreciated.

Michael

Re: Debugging forms

[Josh Canfield <jo...@gmail.com>]

Do your submit buttons have images?

http://www.onenaught.com/posts/382/firefox-4-change-input-type-image-only-submits-x-and-y-not-name

On Fri, Jul 8, 2011 at 10:54 AM, Michael Prescott
<mi...@gmail.com> wrote:
> I have a form that involves a loop, and each row has some <t:submit>
> buttons.  On Chrome, these buttons work just fine (triggering a server-side
> event); in Firefox 4, the form submits, but the submit button's event isn't
> triggered.
>
> What techniques are available for debugging this?  I've got the
> tapestry.events log channel output, which is why I can tell the submit
> button's event handler isn't being triggered, but I'd like to get a bit
> higher up the 'stack'.
>
> Unfortunately, the POST data is incomprehensible, since everything's encoded
> and it seems full of spurious differences (like encoded, transient IDs).
>
> Any tips would be appreciated.
>
> Michael
>

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