I ran into the same issue. In my case, I was updating a child theme when this issue appeared. I then realized it happened on twenty-seventeen theme itself, including the theme demo page–but not on my original child theme before I started updating it.
Through trial and error, I found the change I made to my child theme’s CSS that “unfixed” this behavior. It turns out, setting z-index on the .site-content-contain div fixes it. Don’t ask me why.
.site-content-contain {
z-index:5;
}
This makes absolutely no sense, and shouldn’t do anything related to the fixed images. But it works for me. (It also works on the 2017 demo if I add the style through developer tools.)
As it only happens on Chrome, it seems to be a Chrome bug. I’m on Win 10, Chrome 67.
-
This reply was modified 6 years, 8 months ago by
Brad Brown.