Fix for "Increase generic entity row touch target (4): iOS troubles

[ildar170975]

Breaking change

Proposed change

This whole story:
FR #18461 -> fix #23894 -> issue #23948 -> fix #23953 -> issue #23971 -> fix #23973 -> issue #24009 -> fix #24002

ended up with a fixed look (colored areas are "active"):

Same nice look in Chrome & FF in Win10x64.

But there is an issue #24214 in iOS Companion App & Mac.
I see it in iOS 15.7.x & Mac 10.15.x - both Safari and Chrome.
Names & states are not vertically aligned.

After unsuccessful attempts to fix this behaviour in iOS - I think that REVERTING to the old structure (at least for height) is the best option.
Now it looks like

Active areas became smaller - as they were before 2025.2.
Imho not a big deal if compared with consequences.

Type of change

• Dependency upgrade
• [ x ] Bugfix (non-breaking change which fixes an issue)
• New feature (thank you!)
• Breaking change (fix/feature causing existing functionality to break)
• Code quality improvements to existing code or addition of tests

Example configuration

Additional information

• This PR fixes or closes issue: fixes # Broken alignment of icons on mobile web and app. #24214
• This PR is related to issue or discussion:
• Link to documentation pull request:

Checklist

• The code change is tested and works locally.
• There is no commented out code in this PR.
• Tests have been added to verify that the new code works.

If user exposed functionality or configuration variables are added/changed:

• Documentation added/updated for www.home-assistant.io

[MindFreeze]

I feel like this should be fixable but don't have an iOS device so I'll leave it to someone with one to review

[wendevlin]

@ildar170975 thanks

[ildar170975]

feel like this should be fixable

I hope so. And I will keep testing alternatives. Let’s consider this PR as a quick fix until a proper way to fix iOS specificity is found.

[silamon]

Consider to use fixes https://github.com/home-assistant/frontend/issues/24214 (without the #) to auto close issues when the pull request is merged. In Github it will link the issue and there's will be a slow underline under fixes when you've done it correctly.

[ildar170975]

Consider to use fixes

You are right! Usually do it in cases when I am 100% sure.