-
Notifications
You must be signed in to change notification settings - Fork 2.9k
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
2022.11 b0 - Ugly white card borders #14204
Comments
I'm also getting a thin border around all elements on my dashboards after upgrading to 2022.11.0b0, also showing in Chrome on Android and the HA app on Android. |
I don't know if it's the
|
If you add 'ha-card-border-width: 0px' to your theme file it will remove all the borders until a permanant fix is released. |
This change of appearance is due to the removal of the default box-shadow and the increase of the default border-radius from 4px to 16px (in most cases). This results in a unwanted visable border-radius and destroys the alignment of height and width sizes. For the dev (name withheld) that decided to make these changes, I hope you have a good place to hide when this is released today in 2022.11.0 as you are about to upset a very very high percentage of existing users who are not going to appreciate that there dashboards/tabs are no longer in alignment. |
Now users will have to create a custom theme only to fix the new design. |
I think they were stuck with the old design and now they want to introduce mushroom cards (starting with Tile), they need to change global styling with small touches. It must be complicated for them to take such choices since they know that any little change will break dashboards of users. Still, I personally think that the new default border radius is way to big. |
I just hate that the onus is always on the users to figure out what changed, and how to revert or fix the changes. A simple addition to the patch notes about a breaking change to the design would go a long way. Even better, provide some simple CSS in the patch notes to revert the change in a custom theme until people have the time to migrate. But, no, instead it's a surprise to most users who haven't been following the design changes, and a sudden realization that what was supposed to be a simple version update I didn't expect to spend time on is (was) yet another fiddly task, for really no reason. |
Same problem here. The borders are stupid. There has to be a way to remove them. |
SmarterHomeLife's hack worked for me:
I placed it in my themes file (the filename might vary based on your particular setup), and refreshed my themes by going to Developer Tools > Services > Home Assistant Frontend: Reload themes option, and hitting the Call Service button. You may need to experiment to find the best place for the hack for you, and I suggest making a comment about it in your file, should you want to revert it sometime in the future. |
That didn't do anything for me. Where exactly did you place that line? I tried it in the Global and Cards section with no luck. |
I had to restart HA for the change to take effect, but keep an eye on your theme repository, they are updating with the fix pretty quickly. |
Worked for me. It doesn't require a restart if you use the frontend.reload_themes service. |
I've restarted both just the themes and entire HA. No difference. Please tell me where in the code you placed the line. |
I placed the line directly under the name of each theme. I’m using iOS-themes, which has several different themes listed. To make it easy, I used text replace to replace the "# Global" comment with "ha-card-border-width: 0px" then saved & reloaded my themes. |
That did it. Thanks! |
In general I'm very happy with the HA, but these changes break designs that have cost many hours to thousands of users. I think this change has not been well thought out. |
Removing shadows and adding borders. |
what do u mean by this? are u saying that those things are being changed next release? or? |
I mean - there is a big probability that this may happen. |
This is just business as usual. For years. There's a major disconnect between what the devs like and what the majority of the userbase want. Strap in, we're just in for the ride. |
This is really unbelievable. btw: this is not only affecting user themes but also the standard theme, which looks completely awful now. Are you deliberately trying to scare new users away? |
I consider these changes as BREAKING. Now I am busy with preparing proposals with adapting users' code for the new UI to get an "old look". |
Agreed. I’m baffled that they didn't add it to breaking changes. |
What is really sad is that they ignore us. |
The devs have said on multiple occasions that they don't like giving people options... So we're stuck with either whatever they like, or a third-party/self made theme that will eventually break in a future update. |
Which is perfectly reasonable as giving more options means more effort to keep all of the options up to date. |
I repeated the same many times in Community. |
Hi, |
Go to stack-in-card repo, there is a PR. |
I also found new design with outline less appealing. To be honest - such borders on everything feel so designed 20 years ago... Anyways, here's a fork of the old theme, you cna install that with HACS - works well so far. https://github.com/ChristophCaina/home-assistant-theme-outline-edge |
Interesting.... |
I close the PR as the issues are about stack in card and PR has been open : custom-cards/stack-in-card#47 |
In my case, this works. |
Checklist
Describe the issue you are experiencing
Cards now have white borders in dark mode, which negatively impact the aesthetic of front end dashboards.
Describe the behavior you expected
All front end cards have white borders when in dark mode.
Steps to reproduce the issue
...
What version of Home Assistant Core has the issue?
2022.11 b0
What was the last working version of Home Assistant Core?
2022.10.5
In which browser are you experiencing the issue with?
Safari & Chrome
Which operating system are you using to run this browser?
MacOS Big Sur, Ubuntu
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
The text was updated successfully, but these errors were encountered: