Image min_width
calculated based on device screen size, not window inner width
#320
Replies: 6 comments 7 replies
-
I am not sure if @petarkozul meant for this behaviour but it seems reasonable to me that it would look that way. Most people seem to use panel view full screen? |
Beta Was this translation helpful? Give feedback.
-
I'm sorry that I've not touched this. I fully understand your thoughts. I guess we should consider to use |
Beta Was this translation helpful? Give feedback.
-
Has this already been dealt with? |
Beta Was this translation helpful? Give feedback.
-
For now, I have a solution. Wrap the HA-Floorplan card in a HA conditional card with the corresponding mediaquery's To avoid having the same rules in multiple cards, put them in a separate yaml file and include that in the rules.
in a separate file the rules.
This code is not complete, but you'll get the idea. |
Beta Was this translation helpful? Give feedback.
-
Is there any downside of converting this to using the bower width instead of screen width? As in, will this break any user's implementations that currently exist? If so, perhaps this could be implemented as a non-default setting. |
Beta Was this translation helpful? Give feedback.
-
Perhaps it’s possible to add, Instead of change into. |
Beta Was this translation helpful? Give feedback.
-
When utilizing the variable
image: sizes
entry, the image is selected based on the device screen width, not the window's current width. This matches what the documentation states:For supporting multiple Floorplan images based on the current screen resolution, image can be set to an object that contains a list of image sizes.
This means that when opening a floorplan in a browser, the screen size of the device is the deciding factor, not the actual size of the browser window. I'm not sure if this is intended behavior or not, which is why I would like to discuss it here before creating an issue or pull-request.
Example:
Code Refrerence:
Beta Was this translation helpful? Give feedback.
All reactions