Use attribute picker for sec. info in weather card editor

[spacegaier]

Breaking change

Proposed change

Use attribute picker in the weather card editor.

There are a few somewhat related challenges:

1. Due to the flex shrinking, the "suffix" slot of the used <paper-input> gets too narrow and stacks the clear and menu icons. I wasn't able to get that sorted out via CSS so far with the mixins (--paper-input-suffix). I only could verify via the browser dev tools, that with flex-shrink: 0 applied to the "suffix" <span> the issue disappears.

2. The <ha-switch> is too far to the left as you can see by the shown helper lines. I am unsure whether just moving that instance a bit to the right is the correct approach. I haven't found other places with the same issue, but then again all other usages of <ha-switch> that I found use the some code.

@bramkragten Can you provide some guidance / ideas here?

Type of change

• 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

Additional information

• This PR fixes or closes issue: fixes Dropdown for attribute on Weather Forecast card editor #7325
• This PR is related to issue:
• 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

[spacegaier]

Without that line, the value was not shown in the input until you clicked into the field. All existing usages of <ha-entity-attribute-picker> in the code base set the attribute allow-custom-value. With that set, it works fine, but without this additional option was required.

[bramkragten]

The 2 issues in your description are not specific for this PR right? They are general issues? Could you create an issue for them?

[bramkragten]

Check #7343 for fixing the first.

The second could be fixed with some padding, but please check the material guidelines first.

[spacegaier]

The 2 issues in your description are not specific for this PR right? They are general issues? Could you create an issue for them?

Yes, generic. Is the rest of this PR good from your point of view?

For the other topics I will have a look if I can fix them based on the PR and hint you mentioned. If not, I will create the separate issues.