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
setting all possible actions to none still triggers the pointer handle #15317
Comments
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. |
May be I am getting this issue wrong - but:
Chrome+Win10. |
my issue was made for a glance card. (now notice I made a typo there in the opening lines, but use the correct in the config description.) |
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. |
Keep? |
Checklist
Describe the issue you are experiencing
trying to make an entity not show any possible action by setting:
on an entity, in this case in
type: glance
card, still makes the handle popup, as if there could be some actionthere really should be no pointer change in this case as all are negated
Describe the behavior you expected
show no pointer change when hovering
Steps to reproduce the issue
...
What version of Home Assistant Core has the issue?
2023.2.0
What was the last working version of Home Assistant Core?
No response
In which browser are you experiencing the issue with?
any
Which operating system are you using to run this browser?
Ventura 13.2
State of relevant entities
No response
Problem-relevant frontend configuration
in this case I am trying to create a 'gap' card inside a glance card, but even on a regular card, this should not happen
Javascript errors shown in your browser console/inspector
No response
Additional information
it would be very nice if we could simply set something like:
and not have to use the whole mapping for all 3 actions separately
(aware thats a FR, but just mentioning here)
The text was updated successfully, but these errors were encountered: