Incidently, I had a possibly related problem a while back, also IE8.
Original mail attached.
A wild guess, but it could be something to do with the way IE8 tries to
parallelarise loading and interpreting of js assets.
R.
On Tue, 2011-04-12 at 15:22 +0100, Jim O'Callaghan wrote:
> Can any of the Tapestry committers vet this before I add a JIRA - thanks.
>
> Regards,
> Jim.
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
> For additional commands, e-mail: users-h...@tapestry.apache.org
>
--- Begin Message ---
Hi,
I have a pretty simple standalone login page with a form:
<t:form t:id="login">
<input t:id="oreq" t:type="hidden" />
<label for="email">Email</label><br />
<input t:id="email" t:type="TextField" maxlength="100" /><br />
<label for="password">Password</label><br />
<input t:id="password" t:type="PasswordField" maxlength="20" /><br />
<input type="submit" value="Login" />
</t:form>
On clicking the submit button, IE8 is throwing the following error:
"Exception thrown and not caught tapestry.js line 766 character 8"
On looking at the js, it appears that the form event manager is
undefined.
The POST does get made however, with the appropriate data being sent
back. However it's not ideal. Any idea why this might be happening, or
what (as yet unnoticed) consequences there might be?
Thanks
--- End Message ---
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
