You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In our MAUI application, we are encountering a challenge with maintaining consistent visual states for UI elements. Here's a simplified explanation:
When a parent element is set to a "disabled" state, it overrides the states of its child elements( property value propagation. For example, if a parent is disabled and a child element is set to "selected," the parent's "disabled" state takes precedence, and the child appears disabled as well.
When the parent element's state changes back to "enabled," the child element should return to its "selected" state. However, the current behavior resets the child element to its normal state, not recognizing its previous "selected" state.
This issue makes it difficult to consistently manage visual states in our application, as changes to parent elements inadvertently affect the states of child elements in unintended ways. (CollectionView...)
Despite numerous issues being reported, they end up in the backlog without resolution. This delays our ability to provide a seamless user experience.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
In our MAUI application, we are encountering a challenge with maintaining consistent visual states for UI elements. Here's a simplified explanation:
When a parent element is set to a "disabled" state, it overrides the states of its child elements( property value propagation. For example, if a parent is disabled and a child element is set to "selected," the parent's "disabled" state takes precedence, and the child appears disabled as well.
When the parent element's state changes back to "enabled," the child element should return to its "selected" state. However, the current behavior resets the child element to its normal state, not recognizing its previous "selected" state.
This issue makes it difficult to consistently manage visual states in our application, as changes to parent elements inadvertently affect the states of child elements in unintended ways. (CollectionView...)
Despite numerous issues being reported, they end up in the backlog without resolution. This delays our ability to provide a seamless user experience.
Beta Was this translation helpful? Give feedback.
All reactions