URL Path for Background image in body_background style variable

[Snowhog]

Works great in Firefox, not so much in Safari. In Safari, page scrolling is appallingly SLOW and not smooth. In Safari, if I use the full css_additional.css code (post #13) and keep Style Variable body_background at default settings, page scrolling is responsive and smooth. So I'm sticking with the full css_additional.css code.

[glennrocksvb]

In Safari, page scrolling is appallingly SLOW and not smooth.

That's an interesting behavior in Safari.

So I'm sticking with the full css_additional.css code.

I checked your site and it seems that it still has the body_background stylevar set along with my suggested code in post #14.

[Snowhog]

I am using css_additional.css in only two Styles: KDE Plasma and Default vB5 Style.

Style: KDE Plasma

Style Variable: body_background

Background image: url("core/images/misc/5025.png")
Background Repeat: Repeat

css_additional.css:
body {
background-attachment: fixed;
}


Style: Default vB5 Style

Background image: url("images/css/bckg_page.png?v=3")
Background Repeat: Repeat

css_additional.css:
none

Observed Browser Behavior

Firefox - Smooth scrolling, no page lag with KDE Plasma or Default vB5 Style

Safari - Jerky scrolling, severe page lag with KDE Plasma and smooth scrolling, no page lag with Default vB5 Style​

For the css_additional.css in Default vB5 Style where I say 'none', that means I'm not using any css to override the body_background Style Variable.

[Snowhog]

Interestingly, Safari on my iPhone isn’t affected; no stuttering and scrolling is smooth.

[Snowhog]

My iMac (macOS Big Sur, Version 11.7.10 (20G1427)), Safari is Version 16.6.1 (16615.3.12.11.5, 16615)

My iPhone (iOS 17.4), Safari is Version 17.4.

[Snowhog]

It turns out that using:

body {
     background-attachment: fixed;
}​

in css_additional.css is causing the problem with Safari (on my iMac). I commented it out, and left the image URL in body_background Style Variable and scrolling is again smooth and page navigation responsive as it should be.

Any clue as to why this bit of code would affect Safari this way?

[glennrocksvb]

It might be a Safari bug. If you have access to newer Safari and MacOS versions, then I recommend trying it there.

[Snowhog]

For me, that's not possible. My iMac is from late 2014, and can't run macOS beyond Big Sur, so my Safari version will remain matched to it. This issue isn't a deal breaker by any means. Heck, I don't have to have a background image, or, I just use Firefox to access our Forum.