Homekit dialog is cut-off

[b-reich]

Checklist

• I have updated to the latest available Home Assistant version.
• I have cleared the cache of my browser.
• I have tried a different browser to see if it is related to my browser.
• I have tried reproducing the issue in safe mode to rule out problems with unsupported custom resources.

Describe the issue you are experiencing

The first domains in the "Domains to include" dialog are not user visible.

You cant reach to disable/enable Buttons. Its only working by using the keyboard and navigating there blind.

Describe the behavior you expected

All domains should be visible and user clickable

Steps to reproduce the issue

1. Setup Homekit Bridge
2. (Re-) Configure the existing Homekit Bridge
3. Set Inclusion Modeto include
4. Try to add something like a Button (very first in the alphabet)
   ...

What version of Home Assistant Core has the issue?

2025.1.0

What was the last working version of Home Assistant Core?

No response

In which browser are you experiencing the issue with?

Google Chrome 131.0.6778.205 and Firefox 133.0.3

Which operating system are you using to run this browser?

macOS 15.2

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

[KatyPurry]

I can confirm the bug is still present with he version 2025.1.2.
However, I get this bug as soon as I add the integration

[slawrensen]

This is still an issue. Configuration items that are cutoff cannot be selected from web browsers, only the mobile app. Can this be fixed so the menu is allowed to pop out of the modal?

[ildar170975]

Same with Github integration:

Both using ha-form-multi_select.

[b-reich]

@ildar170975 I already suspected that the UI element would probably be used in several places.

[ildar170975]

This seems to be caused by #21023.
PR changed an inner structure of ha-form-multi_select.
Checked with 2024.12.x - there is no such a glitch.
Asked in #21023 about a possible impact, got no feedback from Devs.

[karwosts]

I think this may fix: #23781

[ildar170975]

@karwosts
Will it cause setting a position: fixed for the .items element?

Also, have you considered this layout?