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
When you set invalid number/value for the color-scheme property (e.g. 13), the appearance of the message strip does not default to an existing color scheme but looks strange, especially for design="ColorSet1" because there is white text on transparent background
Previously there was a built-in mechanism in the framework for fallbacking to the default value when invalid one is set. With 2.0 this has been removed with this change
There are no fallbacks any more. All runtime checks for properties (especially enumerations) are removed. All type checking is left to the TypeScript compiler and assigning an invalid value to an enumeration or a number/boolean field is considered a bug that should be fixed instead of the framework silently masking it by providing a fallback value.
So I don't consider this as bug, if this happens we will ask the developer/consumer to fix the usage.
On CSS level probably we can write some smarter styles to make it better but again we will mask the wrong usage.
Thank you for your feedback regarding this issue. Since you mentioned that this isn't actually an issue, but more of an incorrect usage, I will go ahead and close it. If there are any further details or concerns related to this matter, please feel free to reopen the issue or create a new one.
Bug Description
When you set invalid number/value for the color-scheme property (e.g. 13), the appearance of the message strip does not default to an existing color scheme but looks strange, especially for design="ColorSet1" because there is white text on transparent background
Affected Component
No response
Expected Behaviour
No response
Isolated Example
No response
Steps to Reproduce
design="ColorSet1" color-scheme="13"
Log Output, Stack Trace or Screenshots
No response
Priority
Low
UI5 Web Components Version
2.0.1
Browser
Chrome
Operating System
Windows
Additional Context
No response
Organization
No response
Declaration
The text was updated successfully, but these errors were encountered: