[
https://issues.apache.org/jira/browse/TAP5-410?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12659706#action_12659706
]
Howard M. Lewis Ship commented on TAP5-410:
-------------------------------------------
I'm in search of a more general solution to the problems of pages loading
slower than the JavaScript initializes. I'm thinking of something that puts an
invisible no-click shield over the whole page until the page finishes loading.
But that would be an ugly block of (inline?) JavaScript at the top of every
page. Part of the solution is to put more JavaScript inside attributes,
something I oppose for aesthetic reasons (and because different code, mixins,
etc. will end up fighting over this one favored slot).
> FormFragment 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 statement is not true - see later comments].
--
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]
