Earlier quoted context omitted.
Depends when you view it
"Even a broken clock is right twice a day"
Wristwatch in only HTML/CSS
21–30 of 37 posts
Re: Wristwatch in only HTML/CSS
#22Very cool, but I am still amazed by how CSS animations are killing modern desktop CPU. I guess this is because my Chrome browser is not using GPU acceleration for CSS? If I duplicate 10 times the watch, my CPU hits 100%.
Re: Wristwatch in only HTML/CSS
#23Re: Wristwatch in only HTML/CSS
#24Here's a zero image version: http://codepen.io/anon/pen/rEfKk Using a CSS texture from http://lea.verou.me/css3patterns/
I'm going to take this as a pull request and adjust my pen. How would you like to be credited? (name/link/anything else)
Re: Wristwatch in only HTML/CSS
#25#glass #center #smallHand, #glass #center #midHand, #glass #center #bigHand { -webkit-transform-origin: 0% 50%; }
It's working in your demo, so I'm guessing you simply forgot to copy it over to the exposed CSS source code? Awesome work, by the way! :)
Re: Wristwatch in only HTML/CSS
#26Replace line 58 with a base64 encoding of the image to make it pure HTML/CSS!
I removed the image completely now courtesy of another commenter. Anyhow, wouldn't base64 be cheating? ;)
Re: Wristwatch in only HTML/CSS
#27To me the title is inaccurate but no one else seems to have mentioned it so...
Re: Wristwatch in only HTML/CSS
#28Is it generally accepted that "only HTML/CSS" really means "HTML/CSS/JS"? To me the title is inaccurate but no one else seems to have mentioned it so...
The following JS is only added to start the time at your local time.Re: Wristwatch in only HTML/CSS
#29Aside: the CSS animations absolutely decimate my core i7 PC and almost makes Chrome become unresponsive. The CPU usage is through the roof, can't wait until CSS animations are stable and more widely supported.
Re: Wristwatch in only HTML/CSS
#30Yea, CSS animations are insanely CPU heavy. CodePen has to kill them after 5 seconds to keep the site responsive.