-
Notifications
You must be signed in to change notification settings - Fork 26
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
Display problem: passing by 0 at every value change #33
Comments
Confirming that the issue occurs in Safari on mobile and desktop, too. |
Adding |
There is definitely something fishy with "animation" (and "animateOnInit") in 0.4. |
Link to upstream issue: Mikhus/canvas-gauges#106 |
|
Yes, same thing happens to me on chrome. workaround works....but Animation would be great... |
I think that issue should have been solved with PR#56. |
Nope, I still have the issue even on Firefox... |
Version 0.6 is from Feb/13. PR#56 has been created March/21. I guess, we need a new release. |
Installed version 0.7 and problem still persists... |
Can you try to open the page in private browser window? I remember I had some trouble with my browser cache during testing. Make sure, the new .js file is loaded. |
It seems like the .js was not recreated for version 0.7. Look at the date. As far as I can tell, this complied js does not include the changes. Also, while investigating this, I discovered that the card version is imported from this file: Which still contains 0.0.4, while this file https://github.com/custom-cards/canvas-gauge-card/blob/master/VERSION has the correct version in it. |
I cloned the repo and ran a "npm install; npm run build" and then copied Changed all the
to |
Later releases should fix the issues |
Running HA 0.110.4 and canvas 0.4... Display problem, when the value changes, the ticker is moving to 0 before displaying the correct value... I can send you a small screen recording if necessary (file type not supported here). The problem seems only linked with Google Chrome (with Firefox, I do not have that behavior).
The text was updated successfully, but these errors were encountered: