mirror of
https://github.com/Nezz/homeassistant-visionos-theme.git
synced 2026-05-09 08:25:57 +02:00
[GH-ISSUE #8] Blur doubly applied for custom:mushroom-chips-card #9
Labels
No labels
bug
bug
bug
duplicate
duplicate
pull-request
third party
third party
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/homeassistant-visionos-theme#9
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @basnijholt on GitHub (Sep 8, 2024).
Original GitHub issue: https://github.com/Nezz/homeassistant-visionos-theme/issues/8
Hi @Nezz,
I thought to look up what happened to your awesome work on adding blur to the frontend (previously you mentioned this on https://github.com/basnijholt/lovelace-ios-themes.)
I noticed you created this awesome theme!
I decided to copy the blur bits here (still WIP) and noticed some problems.
For example:
Using
Seems to be fixed by adding
card_mod:However, this is not a nice solution.
Since you seem to have a lot more frontend experience, I thought you might have a better idea.
@Nezz commented on GitHub (Sep 9, 2024):
Sounds like an issue with mushroom-chips-card. Is
ha-cardnested three times in that case?@basnijholt commented on GitHub (Sep 10, 2024):
It is
custom:mushroom-chips-cardnested inentities. So nested twice (depending on your counting ;)@Nezz commented on GitHub (Feb 12, 2025):
I checked this and the backdrop filter should be disabled on the mushroom chips card here:
github.com/piitaya/lovelace-mushroom@fea08b4534/src/cards/chips-card/chips-card.ts (L120)I'm not a mushroom user, so I don't feel like I have enough context to contribute as it might break things elsewhere without a good understanding of where these cards might show up.
@Nezz commented on GitHub (Aug 10, 2025):
The issue should be fixed in release 2.0, let me know if it doesn't work.