Enhancement
Major
Detail
Bugfix
Detail
#26484
In-app template for grid and tables: Function "Verifier for use as list item" does not get component model
#26885
Constraints on declarative forms with arguments from a container reference lead to errors for new elements
#26922
With generated subject classes, a default provider of an attribute in a non-structure class does not get a create context
Bugfix
Detail
#26928
Hidden component does not appear anymore, although it gets a supported model
If a component does not derive its authorization object from its model but from another component channel, its visibility may not be adjusted correctly when the model is changed. When the model is changed, the component tries to calculate whether its visibility state has changed. To do this, it calculates the visibility with its old model and with its new model. Only if the state differs it informs about a visibility change. But if the visibility does not depend directly on the model at all, this check is wrong and possibly too few events are sent for a visibility change. As a result, a component either does not fade out or does not fade in again.
Test
- Configure view with security master component that gets its authorization object from a component channel.
- Check that the view fades in or out depending on the object on the channel.