/CC @cvrebert @connor @connors @mdo
Note that I left the csslint target out of tests on purpose since it fails due to #390. When that issue is fixed, we should add it in tests.
I'm guessing by all the reordering that we have some property order changes to make to the source Sass files?
Also, is there a way in CSScomb (I haven't checked yet) to remove the spaces between values in the rgba() colors?
We could change some stuff around in Sass files indeed.
For rgba() I can't find any info how to remove the spaces so far.
/CC @connors: maybe you are up to changing the properties order in the Sass files after this is in 👼
you know it. ❤️
@XhmikosR Would you rather me go in and work on fixing the property order in this pull request? Or do you just wanna get this in and I get follow up?
I think it will be better if we merged this separately. Did you review the rest of the changes? If you agree I'll merge this and you can work on the rest.
Remove duplicate properties.
Remove unit from zero.
Add CSSLint support.
Add CSSComb support taken from Bootstrap.
@connors: I don't suppose you wanted to use
@include transform(translate3d(0, 0, 0) translateY(0));
Though translate3d should be enough here.
Yeah, translate3d covers it. Is there a reason to use this rather than translateY(0)? I figured we only needed to override the Y value.
Ah I just saw your original comment. I thought for sure that translateX/Y were hardware accelerated though. The animations are so much smoother that transitioning left or right values.
OK so this patch was right after all :)
And yeah, not everything is hardware accelerated on iOS it seems.
lol ok I should read everything before I post comments. See this comment on the issue you referenced:
It looks like translateX/Y is accerated afterall. That's why the issue was closed.
OK so this should be posted in #495 :P
BTW, somewhere along the way it seems the mobile navbar broke for docs...