frontend
                                
                                 frontend copied to clipboard
                                
                                    frontend copied to clipboard
                            
                            
                            
                        Calendar card in month view and panel type does not vertically fill the screen
Checklist
- [X] I have updated to the latest available Home Assistant version.
- [X] I have cleared the cache of my browser.
- [X] I have tried a different browser to see if it is related to my browser.
Describe the issue you are experiencing
I have a view set to type: panel with a calendar card. When set to month view, the calendar only fills ~50% of the available vertical space resulting in hidden ("+X more") events that could be displayed if the calendar were configured to use all of the available space.
Describe the behavior you expected
The default calendar view (accessed via the sidebar) fills all of the available space and is how the calendar card should work as well.
Steps to reproduce the issue
- Create a new view and set it to type: panel
- Add a calendar card
- Set the calendar card to Month view
- Tap the Sidebar Calendar | Month view to compare
What version of Home Assistant Core has the issue?
N/A
What was the last working version of Home Assistant Core?
N/A
In which browser are you experiencing the issue with?
Multiple
Which operating system are you using to run this browser?
N/A
State of relevant entities
No response
Problem-relevant frontend configuration
No response
Javascript errors shown in your browser console/inspector
No response
Additional information
No response
There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.
This is still an issue that I hope can be addressed in a future update.
There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.
I was able to reproduce the issue. Bump for hoping this gets adressed.
There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.