Re-enabling Attributes display on /developer-tools/state should keep the filtered value or filtering should be cleared on disabling

Mincka commented 7 months ago

Checklist

[X] I have updated to the latest available Home Assistant version.
[X] I have cleared the cache of my browser.
[X] I have tried a different browser to see if it is related to my browser.
[X] I have tried reproducing the issue in safe mode to rule out problems with unsupported custom resources.

Describe the issue you are experiencing

If you filter the entities in the Developer tools by with an Attributes filter, then uncheck and recheck the Attribute checkbox, the filtering stays the same but the filter attributes has disappeared. It's not an an expected behavior since you cannot tell anymore why the filtering stays applied.

Describe the behavior you expected

Option 1) Current Filter attributes should be set back when "Attributes" checkbox is reenabled. Option 2) Filtering by Attributes should be cleared when "Attributes" checkbox is disabled, so renabling it with nothing would be consistent with the displayed results.

Steps to reproduce the issue

Field content is empty but the previous filtering is still applied.

What version of Home Assistant Core has the issue?

2024.4.0b0

What was the last working version of Home Assistant Core?

No response

In which browser are you experiencing the issue with?

Latest version of Edge and Firefox

Which operating system are you using to run this browser?

Windows 11 23H2

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

github-actions[bot] commented 4 months ago

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

Mincka commented 4 months ago

Still there

github-actions[bot] commented 1 month ago

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

Mincka commented 1 month ago

Not stale

home-assistant / frontend