[TAP5-410] FormFragment validates non-displayed fragments

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Invalid
• Affects Version/s: 5.0.17, 5.0.18
• Component/s: tapestry-core
• Assignee: Unassigned
• Reporter: Geoff Callender
• Created: 11/Dec/08 10:12
• Updated: 02/Apr/12 11:56
• Resolved: 04/Mar/09 19:23

Description

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 statement is not true - see later comments].

Issue Links

• is cloned by: TAP5-1892 FormFragment validates non-displayed fragments (reopen)