[
https://issues.apache.org/jira/browse/WICKET-2579?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12779472#action_12779472
]
Erik van Oosten commented on WICKET-2579:
-----------------------------------------
This requires an entirely new implementation of TabbedPanel. The current tabbed
panel is based on the idea that only the visible tab is rendered. What is
needed to implement what you want is to render all tabs to the browser and then
only display one of the panels at a time. This can only be done with javascript
(another departure of the current TabbedPanel implementation).
> tabbedpanel (and ajaxtabbedpanel) only submit the selected tab. A mode which
> instead submits all loaded tabs would be helpful.
> ------------------------------------------------------------------------------------------------------------------------------
>
> Key: WICKET-2579
> URL: https://issues.apache.org/jira/browse/WICKET-2579
> Project: Wicket
> Issue Type: Wish
> Components: wicket-extensions
> Affects Versions: 1.4.3
> Reporter: Roger Armstrong
>
> If I want to split the contents of a form across multiple tabs (for example a
> user profile form split into basic and advanced settings), there seems to be
> no way to validate the form properly.
> The user should be able to fill out, say, first name and last name in the
> basic tab, then switch to the advanced tab and fill out some settings there,
> then click the Save button. If the user forgot to fill out a required field
> on the basic, (say, email address), there's no way to handle this (because
> the first tab is already gone when you switch to the second tab).
> I've tried to use an AjaxFormValidatingBehavior on blur of all form
> components, but this is not a good solution since validation occurs on lost
> focus instead of when the user clicks the Save button.
> What I would like would be that the TabbedPanel keeps all visited panels
> around (but all hidden except the selected tab) so that they are all
> submitted together. That way, you have lazy loading, but standard submit and
> validate behavior (at the expense of keeping the loaded panels around).
> This seems like a fairly standard pattern for using a tabbed panel, so it
> would seem useful to have it in the "standard" tab panel instead of everyone
> having to reinvent it (like at
> http://www.xaloon.org/blog/advanced-wicket-tabs-with-jquery).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
