[
https://issues.apache.org/jira/browse/WICKET-2063?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12669187#action_12669187
]
Juergen Donnerstag commented on WICKET-2063:
--------------------------------------------
I think the patch is going into the right direction. Currently
ENABLED_IN_HIERARCHY_CACHE_KEY is reset in Component.detach, but it should be
internalBeforeRender.
The updated patch attached
- changes ENABLED_IN_HIERARCHY_CACHE_KEY from MetaData to simple Boolean. There
is no good reason why this is a MetaDat
- updates places where isEnabled() is used but isEnabledInHierarchy is
better/faster because of the cached value.
> Wizard buttons (previous / finish) aren't enabled when they should be
> ---------------------------------------------------------------------
>
> Key: WICKET-2063
> URL: https://issues.apache.org/jira/browse/WICKET-2063
> Project: Wicket
> Issue Type: Bug
> Components: wicket-extensions
> Affects Versions: 1.4-RC2
> Reporter: Jeremy Thomerson
> Fix For: 1.4-RC2
>
> Attachments: 2063.patch, 2063.patch
>
>
> When using the Wizard component in 1.4-SNAPSHOT (sometime after 1.4-RC1), the
> previous and finish buttons don't enable when they should. I have found that
> this is because isEnabledInHierarchy is called multiple times, with the first
> time being during the POST process, before the wizard step is advanced to the
> next step. Since the step has not advanced when isEnabled is calculated, you
> get the following behavior:
> 1 - click "next" from first step to second - the "previous" button should be
> enabled, but it's not
> 2 - the "finish" button never is enabled, even on the last step
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
