With these it helps I ran into this issue as well. The problem is that google maps forces GPU compositing on all it's mapping DOM elements via -webkit-transform: translateZ(0); To fix this issue, you can force GPU compositing on all your fixed positioned elements by adding -webkit-transform: translateZ(0); to each fixed element
How to control the draw order of overlapping elements with CSS3 rotate3d and transformZ?
it should still fix some issue will-change basically does the same thing (as of today) as the translateZ(0) hack: it pulls the element out onto a new rendering layer. The difference is that will-change is telling the browser your intent, namely, that you will be changing this property; whereas with translateZ(0) that is merely a coincidental side effect. So will-change is just a more modern way of accomplishing the same thing, and as such, it's also less widely supportedthan 3D transforms.
I wish this helpful for you Flipping twice would be \f -> flip (flip f), or flip . flip. This would indeed have the type (a -> b -> c) -> (a -> b -> c). What you are doing here instead is applying flip on the flip function, i.e. flipping flip's argument order. So if we start with
flip :: (a -> b -> c) -> b -> a -> c
-- and, as the type of the argument
flip :: (a' -> b' -> c') -> b' -> a' -> c'