Title with visibility condition adds extra space above dashboard when condition not met

[tigattack]

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.
• [x] I have tried reproducing the issue in safe mode to rule out problems with unsupported custom resources.

Describe the issue you are experiencing

When a title card (introduced in 2025.3) is added with a visibility condition (screen 'mobile', in my case), there is extra space added above the 'main' dashboard below when the visibility condition is not met.

Describe the behavior you expected

I would expect the dashboard to look exactly the same as before when the visibility condition is not met.

Steps to reproduce the issue

1. Add title card with visibility condition
2. View dashboard in scenario where condition is not met
3. See issue.

What version of Home Assistant Core has the issue?

core-2025.3.3

What was the last working version of Home Assistant Core?

core-2025.2.x

In which browser are you experiencing the issue?

Firefox 136.0, Chromium 135.0.6999.0

Which operating system are you using to run this browser?

macOS Sonoma 14.5

State of relevant entities

Problem-relevant frontend configuration

header:
  card:
    type: markdown
    text_only: true
    content: '# 🏠 Hello, {{ user }}! 👋'
    visibility:
      - condition: screen
        media_query: '(min-width: 0px) and (max-width: 767px)'

Javascript errors shown in your browser console/inspector

Additional information

With conditional title card where condition is unmet/false:

Without card:

[github-actions[bot]]

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.

[tigattack]

Still an issue.

[github-actions[bot]]

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.