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
I haven't tested if it is because of this, but pretty sure it because you set the min and max in the styles. You need to put those config keys in the root of the slider config.
The same is true with the showMin and disableScroll. You should only add css styling inside the styles key.
So your example should look like:
Hi, this solution seems to work only if the card is in the "normal" yaml flow of the page.
But it no longer works if I open the card in a popup with browser_mod.
In this case, while maintaining the directions you gave, the max does not lock at the level set in the code.
I specify that this anomaly occurs only for the MAX value and not for the MIN... There is that a reason?
Off-topic:
I anticipate that there are other anomalies with "my-card.js" that you can already see in yellow color in the image I am about to provide you. For which I will open a specific issue. (I have verified that these additional anomalies always occur, even without using browser_mod)
Anyway, returning to the topic, an error appears on the page and, moreover, in the console it reads:
connection-mixin.ts:156 Uncaught (in promise)
{code: 'invalid_format', message: 'Invalid value for input_number.slider_intensity: 6.0 (range 1.0 - 5.0)'}
code
:
"invalid_format"
message
:
"Invalid value for input_number.slider_intensity: 6.0 (range 1.0 - 5.0)"
Current Behavior
when setting the max option in the card config, the card allows the value to be set higher then max value.
Expected Behavior
when sliding up i expect the value to stop at what was set under the max setting.
in my case TV volume can not be set above 20.
Steps To Reproduce
add the following card code
slide volume and observe setting change on the device
Environment
Anything else?
No response
The text was updated successfully, but these errors were encountered: