-
Notifications
You must be signed in to change notification settings - Fork 675
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
Animated icons broken on Chrome #27
Comments
Yeah, that's pretty unreadable 😐 Taking a quick glance at "My splitted "custom_fields" code after update:" (entity on) You've got Try this in your browser
|
Thank you for your kind reply matt and please excuse the mess with my code. I have managed to make it work deleting this part of the SVG:
This SVG display the good animation in Chrome:
I still don't understand why the piece of code i have delete was causing the problem. Thank you for your support. |
Fixed with last |
Hello matt8707,
First of all, i would like to thank you for your amazing work and generosity.
Your animated buttons completely blew my eyes when i saw them. I didn't know it was even possible to do that.
I have digged into your code and found how to implement the animations for my buttons and i also learned how to create my owns on SVGator.
Sorry if my question is not related to your config or personal buttons but i'm struggling with this since few days now as i'm far from being an expert in css templating.
My animations were working fine on all browsers but since last "Chrome" update they are kind of broken on this particular browser and also on the Android App.
I have split my SVG code and it partially fixed the animations display, but i don't understand how to completely resolve this issue and if this is even possible.
Here is my code before Chrome update:
The correct behavior before update:
The wrong behavior after update:
The partially corrected behavior after update:
My splitted "custom_fields" code after update:
Your SVG codes are so clean compare to the one i export from SVGator, i can understand Chrome is more tolerant with them.
Thank you in advance for your help and again thanks for the fabulous inspiration you gave me and countless Home Assistant users.
The text was updated successfully, but these errors were encountered: