-
-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Glitches with in_card and Home Assistant 2022.11 #21
Comments
Issue also appears with the no_card option as well. |
So it looks like we probably need a 'border: none' in: https://github.com/jcwillox/lovelace-canary/blob/main/src/const.ts So we end up with something like:
|
As a workaround, you can use the following in Lovelace:
Full example, where I had a horizontal line going through the 'boost' buttons:
|
Yeah, this is definitely an issue, I'll try to get it fixed soon 👍 |
Some news about that @jcwillox ? |
Yeah very sorry that it's taken so long, I have been very busy with the job I just started + other things, I was planning to sort it out this weekend but there was a breaking change with HA 2022.12 for my other plugin paper-buttons-row, which took priority as there was no simple fix for it. That's done now so hopefully the canary fix will be out tomorrow night. It also took a little longer as there hasn't been a release since I migrated the codebase to typescript so I need to make sure I didn't break anything back when I did that. (Honestly no idea where the last month went 👀) Just a reminder to anyone that stumbled upon this, that this will temporarily fix the issue canary_style:
border: none |
So I've released 0.4.0 which should fix the issues with I thought I'd also mention that it appears custom-cards/stack-in-card is no longer maintained and if you are looking for a dedicated stack-card that supports the UI editor ofekashery/vertical-stack-in-card looks like a good alternative. |
Quick test on in_card seems to work fine. |
Seems to have fixed the issue for me thanks 😁 |
@jcwillox i think its the same issue again with the latest version, tested with: 2024.8.2
|
The problem
With latest Home Assistant, there are glitches where the cards join. Here a capture of three cards in one:
What version of Canary has the issue?
0.3.4
What version of Home Assistant are you running?
Home Assistant 2022.11.1
What version of the Frontend are you running?
Frontend 20221102.1
Example YAML snippet
Anything in the logs that might be useful for us?
Nothing
Additional information
None
The text was updated successfully, but these errors were encountered: