[
https://issues.apache.org/jira/browse/WICKET-7101?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17834810#comment-17834810
]
ASF subversion and git services commented on WICKET-7101:
---------------------------------------------------------
Commit b2996ea5c698ed87a1482658401be6a305434e9b in wicket's branch
refs/heads/dependabot/maven/org.apache.maven.plugins-maven-enforcer-plugin-3.4.1
from reiern70
[ https://gitbox.apache.org/repos/asf?p=wicket.git;h=b2996ea5c6 ]
[WICKET-7101] The label associated with form component should always be
rendered when the form component is rendered via AJAX. This way we ensure the
state of the label is consistent with form component's state. This introduces a
new wicket attribute wicket:auto that controls that auto-label is bound to form
component. Also introduces a new updateAutoLabelsTogetherWithFormComponent
markup setting that allows to set new behavior as default one for all
auto-labels
> auto-label is not automatically updated when related form component is
> updated.
> -------------------------------------------------------------------------------
>
> Key: WICKET-7101
> URL: https://issues.apache.org/jira/browse/WICKET-7101
> Project: Wicket
> Issue Type: Improvement
> Reporter: Ernesto Reinaldo Barreiro
> Assignee: Ernesto Reinaldo Barreiro
> Priority: Major
> Fix For: 10.1.0, 9.18.0
>
>
> Auto-labels are somewhat disconnected from FormComponent they are bound to in
> the sense that:
>
> * You can modify the form component (e.g. if it is required) and update that
> component via AJAX and
> * Autolabel will stay with a stale state: i.e. still with the required CSS
> class
> This should be fixed with
>
> [https://github.com/apache/wicket/pull/812]
>
> This PR introduces:
> * a new tag *wicket:auto='true|false'* that allows to set some auto label as
> updatable always that form component is updated (via AJAX or web socket
> request).
> * a new boolean flag on markup-settings that allows to set this new behavior
> as application default. By default, the flag is set to false thus that
> applications keep existing behavior.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
