dmatik
October 3, 2024, 11:02am
1824
Hi,
Anybody able to change the font-family of new titles badges in 2024.10.0, in section view?
I was able to fix the title itself font family, but not able to get to badges.
Meaning is in theme of course.
Thanks in advance.
at the end of the day, I made 2 classes:
ha-card.class-section-heading .container {
background: var(--background-color-off);
--ha-heading-card-title-color: var(--text-color-off) !important;
--ha-heading-card-title-font-size: 20px !important;
--ha-heading-card-title-font-weight: 400;
height: 24px;
padding: 12px 8px 12px 12px;
}
ha-card.class-section-heading-no-color .container {
/*background: var(--background-color-off);*/
/*--ha-heading-card-title-color: var(--text-color-off) !important;*/
--ha-heading-card-title-font-size: 20px !important;
--ha-heading-card-title-font-weight: 400;
height: 24px;
padding: 12px 8px 12px 12px;
}
so I can do a generic:
type: heading
heading: Schakelaars
heading_style: title
card_mod:
class: class-section-heading
but, when I require some colorized notification in that header, I can combine the class with a local card_mod for the colors, depending on a state:
- type: heading
heading: Aanwezigheid
heading_style: title
card_mod:
class: class-section-heading-no-color
style: |
ha-card.type-heading {
{% set thuis = is_state('binary_sensor.familie_thuis','on') %}
background: {{'green' if thuis else 'dimgray'}};
--ha-heading-card-title-color:
{{'var(--active-color)' if thuis else 'black'}} !important;
}
for now this is flexibility enough.
I do still hope to be able to find the element for the individual entity in the badges in the header
matata
(Martin Prochazka)
October 4, 2024, 6:54am
1826
Hello and pleaseā¦ is possible styling new badge?
type: entity
show_name: false
show_state: true
show_icon: true
entity: input_boolean.vacuum_automaticke_vysavani_zahajeno
color: ""
card_mod:
style:
/*code*/
TimoJ
October 4, 2024, 10:38am
1827
HA 2024.10 has added āfrom the topā open animations to all dialog/more-info popup windows (or made them more visible/annoying than before). Is it possible to remove them or adjust animation timing with a card mod theme?
I canāt figure out what I should change.
It could be caused by a slower opening the popups. Check if this happens on a fresh HA setup or in a safe mode.
no, itās new, and though initially I liked it on the restart menu, (for me that is not inside the user side of HA), I have grown to find them truly obnoxious in all confirmation popups etc etc.
There must be some setting we can kill the animation forā¦
letās find the PR that added it
suppose its the move to ha-md-dialog
home-assistant:dev
ā home-assistant:dialog-restart-md
opened 02:31PM - 19 Sep 24 UTC
<!--
You are amazing! Thanks for contributing to our project!
Please, DO Nā¦ OT DELETE ANY TEXT from this template! (unless instructed).
-->
## Breaking change
<!--
If your PR contains a breaking change for existing users, it is important
to tell them what breaks, how to make it work again and why we did this.
This piece of text is published with the release notes, so it helps if you
write it towards our users, not us.
Note: Remove this section if this PR is NOT a breaking change.
-->
## Proposed change
<!--
Describe the big picture of your changes here to communicate to the
maintainers why we should accept this pull request. If it fixes a bug
or resolves a feature request, be sure to link to that issue or discussion
in the additional information section.
-->
For the restart dialog use the material/web based ha-md-dialog instead of the ha-dialog.
- Add workaround for ha-md-dialog to open a dialog inside a dialog
- Add chevrons to restart actions
## Type of change
<!--
What type of change does your PR introduce to the Home Assistant frontend?
NOTE: Please, check only 1! box!
If your PR requires multiple boxes to be checked, you'll most likely need to
split it into multiple PRs. This makes things easier and faster to code review.
-->
- [x] Dependency upgrade
- [ ] 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
<!--
Supplying a configuration snippet, makes it easier for a maintainer to test
your PR.
-->
```yaml
```
## Additional information
<!--
Details are important, and help maintainers processing your PR.
Please be sure to fill out additional details, if applicable.
-->
- This PR fixes or closes issue: fixes #
- This PR is related to issue or discussion:
- Link to documentation pull request:
## Checklist
<!--
Put an `x` in the boxes that apply. You can also fill these out after
creating the PR. If you're unsure about any of them, don't hesitate to ask.
We're here to help! This is simply a reminder of what we are going to look
for before merging your code.
-->
- [ ] 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][docs-repository]
<!--
Thank you for contributing <3
-->
[docs-repository]: https://github.com/home-assistant/home-assistant.io
## Summary by CodeRabbit
- **New Features**
- Enhanced dialog functionality allowing multiple dialogs to overlay.
- Transitioned to a Material Design dialog for improved visual consistency.
- Added close button with an icon in the dialog header for better accessibility.
- Updated list items for streamlined interactivity and context.
- Improved layout consistency with new padding for slotted content.
- **Bug Fixes**
- Improved state management when closing dialogs.
- **Chores**
- Simplified internal methods for cleaner code and maintainability.
and
home-assistant:dev
ā home-assistant:dialog-box-md
opened 12:03PM - 17 Sep 24 UTC
<!--
You are amazing! Thanks for contributing to our project!
Please, DO Nā¦ OT DELETE ANY TEXT from this template! (unless instructed).
-->
## Breaking change
<!--
If your PR contains a breaking change for existing users, it is important
to tell them what breaks, how to make it work again and why we did this.
This piece of text is published with the release notes, so it helps if you
write it towards our users, not us.
Note: Remove this section if this PR is NOT a breaking change.
-->
## Proposed change
<!--
Describe the big picture of your changes here to communicate to the
maintainers why we should accept this pull request. If it fixes a bug
or resolves a feature request, be sure to link to that issue or discussion
in the additional information section.
-->
Us the material/web dialog ha-md-dialog for all dialog-boxes.
## Type of change
<!--
What type of change does your PR introduce to the Home Assistant frontend?
NOTE: Please, check only 1! box!
If your PR requires multiple boxes to be checked, you'll most likely need to
split it into multiple PRs. This makes things easier and faster to code review.
-->
- [ ] Dependency upgrade
- [ ] Bugfix (non-breaking change which fixes an issue)
- [ ] New feature (thank you!)
- [ ] Breaking change (fix/feature causing existing functionality to break)
- [x] Code quality improvements to existing code or addition of tests
## Example configuration
<!--
Supplying a configuration snippet, makes it easier for a maintainer to test
your PR.
-->
```yaml
```
## Additional information
<!--
Details are important, and help maintainers processing your PR.
Please be sure to fill out additional details, if applicable.
-->
- This PR fixes or closes issue: fixes #
- This PR is related to issue or discussion:
- Link to documentation pull request:
## Checklist
<!--
Put an `x` in the boxes that apply. You can also fill these out after
creating the PR. If you're unsure about any of them, don't hesitate to ask.
We're here to help! This is simply a reminder of what we are going to look
for before merging your code.
-->
- [ ] 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][docs-repository]
<!--
Thank you for contributing <3
-->
[docs-repository]: https://github.com/home-assistant/home-assistant.io
## Summary by CodeRabbit
- **New Features**
- Introduced a new dialog structure with enhanced action handling.
- Updated dialog buttons for improved clarity and functionality.
- **Improvements**
- Added specific styles for alert dialogs to ensure consistent width.
- Enhanced responsiveness of non-alert dialogs with media queries.
- Improved rendering logic for dialog titles and content.
- **Bug Fixes**
- Improved handling of dialog states for cancellation and confirmation actions.
I really do not recall a similar PRā¦ Will check it.
(have not noticed any changes in showing popups by my eyes)
TimoJ
October 4, 2024, 11:50am
1831
It happens also in safe mode. Even restart options popup appears slowly/animated.
I also found only this md-dialog-box related PR but not sure if it is relatedā¦
TimoJ
October 4, 2024, 12:01pm
1834
Animation also makes more info charts to appear laggy. First I thought that my database was working very slowly but itās just the animationā¦ I can also see right side scrollbar appearing and then disappearing when the popup is fully shown. It looks bad.
If this is not only about an animation but also about a general look - would be great to have 2 pictures side-by-side for comparing: old vs new.
(cannot do it myself, left & do not have access to PC)
at least I have my squared boxes back
md-dialog-container-shape-start-start: var(--ha-card-border-radius)
md-dialog-container-shape-start-end: var(--ha-card-border-radius)
md-dialog-container-shape-end-start: var(--ha-card-border-radius)
md-dialog-container-shape-end-end: var(--ha-card-border-radius)
no other overall variable, had to set all cornersā¦
the silly animation is still there though
psyspy
(Psyspy)
October 5, 2024, 4:00pm
1837
Hello! I am trying to increase the icon size of the built-in weather card (forecast) using card mod. I am a newbie with CSS. I went to the design inspector in Firefox and inspected the first icon on the card. Hereās the screenshot:
If I change the width
and height
of .forecast-image-icon
to 64px in the design inspector, it works as intended. All the forecast icons get bigger. I have another card for weekly forecast. Itās icons get bigger too, which is fine. I think I updated the .forecast-image-icon
class attributes globally.
Anyways, I tried this with the card mod:
show_current: false
show_forecast: true
type: weather-forecast
entity: weather.blah
forecast_type: hourly
theme: Animated Weather Icons Filled
card_mod:
style: |
ha-card div.forecast-image-icon
{
width: 64px;
height: 64px;
}
It didnāt work. I canāt post more pictures since I am a new user. Let me post them in a new post. I appreciate any help.
psyspy
(Psyspy)
October 5, 2024, 4:05pm
1838
Hereās the image after my card mod changes:
Not what I expected.