[ 
https://issues.apache.org/jira/browse/TAP5-410?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12655927#action_12655927
 ] 

Sergey Chaban commented on TAP5-410:
------------------------------------

Another issue is when the page loads for too long 
(http://jumpstart.doublenegative.com.au:8080/jumpstart/examples/wizard/usingformfragments
   loads for about 10-15 secs for me) - not waiting for the complete page load 
causes validation error: "You must provide a value for Name." - which is to be 
validated in the next fragment.

I guess it is because button event bindings are located at the bottom of the 
page in

    Tapestry.onDOMLoaded(function() ... 

and are not fired at the moment of form submission

Fails in Forefox 3.0.4, IE 7.0.6001.18000

> FormFragment with IE validates non-displayed fragments
> ------------------------------------------------------
>
>                 Key: TAP5-410
>                 URL: https://issues.apache.org/jira/browse/TAP5-410
>             Project: Tapestry 5
>          Issue Type: Bug
>          Components: tapestry-core
>    Affects Versions: 5.0.17, 5.0.18
>            Reporter: Geoff Callender
>
> A user of JumpStart pointed this out in the wizard that uses FormFragments 
> http://jumpstart.doublenegative.com.au:8080/jumpstart/examples/wizard/usingformfragments
> In this wizard each step is a separate FormFragment.  The sequence to make it 
> fail in IE 7 is: in step 1 enter a value and press Next, in step 2 (which is 
> a different fragment) press Prev without entering a value, in step 1 press 
> Next.  Kaboom! The validation error that is displayed belongs to step 2, not 
> step 1.
> This works fine in Safari 3.2.1 and Firefox 3.0.4 but not in IE 7.0.5730.13.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to