[
https://issues.apache.org/jira/browse/WICKET-5411?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Igor Vaynberg updated WICKET-5411:
----------------------------------
Description:
The problem with auto labels is that once they are rendered the only way to
update their `error`/`required` css classes during ajax requests is to update
some parent since auto components cannot be targeted directly. however, when
dealing with forms we may not necessarily want to repaint components because we
may lose state.
This issue solves the problem by tracking state changes in form components that
have auto labels and updating their css classes on all ajax requests.
disabled by default in 6.13, always enabled in 7.0
was:
The problem with auto labels is that once they are rendered the only way to
update their `error`/`required` css classes during ajax requests is to update
some parent since auto components cannot be targeted directly. however, when
dealing with forms we may not necessarily want to repaint components because we
may lose state.
This issue solves the problem by tracking state changes in form components that
have auto labels and updating their css classes on all ajax requests.
> Improve AutoLabels to update their CSS dynamically
> --------------------------------------------------
>
> Key: WICKET-5411
> URL: https://issues.apache.org/jira/browse/WICKET-5411
> Project: Wicket
> Issue Type: Improvement
> Components: wicket
> Reporter: Igor Vaynberg
> Assignee: Igor Vaynberg
> Fix For: 6.13.0, 7.0.0
>
>
> The problem with auto labels is that once they are rendered the only way to
> update their `error`/`required` css classes during ajax requests is to update
> some parent since auto components cannot be targeted directly. however, when
> dealing with forms we may not necessarily want to repaint components because
> we may lose state.
> This issue solves the problem by tracking state changes in form components
> that have auto labels and updating their css classes on all ajax requests.
> disabled by default in 6.13, always enabled in 7.0
--
This message was sent by Atlassian JIRA
(v6.1#6144)
