João Cunha

I tweaked the `update()` function to prevent constant recalculation. Indeed, it somewhat defeats the precision of the library, but it sorts this issue. This is what it looks like, now:...

Hey @lighttroupe! That was a rather hacky solution to prevent it from recalculating all the time. Think we should ping @jackmoore, the maintainer of the library, about this.

+1, specially for CSRF tokens. I'm currently experiencing this issue. @ded is this something you'd be interested in adding?

@ded xmas ping! :)

@iamvdo in a perfect world, it would work automagically for both cases - px to rem and rem to px. Then, a flag could be set on config to disable...

@robwierzbowski writing in px is easier, fool-proof, requires absolutely no math, and "it just works". In fact, people have been writing in px from way before the advent of CSS....

+1. A single class approach also works for that: ``` css .top-menu [class^="icono-"] { font-size: 16px; } .sidebar [class^="icono-"] { font-size: 24px; } ``` Not to mention media queries.

@adamschwartz I don't think non-integer would cause any side effects as long as we're using `em`s. As a matter of fact, even non-integer pixels may round very nicely, [as you...

Maybe I was not clear also :) This is a quick hack I came up with to show a proof-of-concept: (focus only on the `check` icon)  And this is...

Ok, now I see what you mean. Can't think of any other solution other than abiding to safe base font-sizes. That would most likely require some tweaking on the icons...