Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
-
@nbamaral yeah, I could have done the math myself and use the results directly on CSS, but I wanted it to be dynamic, so I wouldn't have much trouble if the client came back and said something like "can you add another element?"
-
-
@shellbug Try downloading Firefox nightly or Developer Edition and see if it also happens there. Chances are it won't, the CSS engine was built anew.
-
@brainlessdev cool! But normal users won't use that, tho.
-
@shellbug
Did a few interactive thingies with pure css, and they worked great in all browsers, the advantage being working with plain ints for rotation.
It takes some work understanding what's the rotation point though.
More complex diagrams I go svg all the way, it's easy to script them too (generate there dynamically) or animate parts of it.
Best of luck 😊
Fuck Firefox's CSS engine! Why is it so fucking buggy?
I needed to position some elements in a circle, so I used Math.cos(Math.PI / 2) to calculate their x positions. So, mathematically speaking, that should return 0, right? Turns out in JS it doesn't (because fuck precision). It actually returns 6.123233995736766e-17 and I was using that in the style, like top: offset + that.
In chrome it was working perfectly, but in Firefox all hell broke loose. All animations stopped working, scripts stopped working, demons were eating people alive.
And I lost hours hunting that down. My fault because I should have tested it immediately on other browsers, but fuck!
rant