Photos Pixelating?
Race Director
Joined: Jul 2000
Posts: 10,777
Likes: 199
I'm seeing that but it also has other pics in a group that includes other pics in the thread that can be indexed through.
Am also getting apostrophies in post texts showing up as blank squares. This started at the same time as the picture issue.
Mac OS/ Safari on iMac. Version 15.4 (15613.1.17.1.11, 15613)
Am also getting apostrophies in post texts showing up as blank squares. This started at the same time as the picture issue.
Mac OS/ Safari on iMac. Version 15.4 (15613.1.17.1.11, 15613)
Racer
Joined: Jan 2022
Posts: 270
Likes: 209
IB Staff
Joined: Feb 2009
Posts: 10,575
Likes: 4
The issue is not specific to CorvetteForum. It's related to the code that is used to load the pictures. However, it's not used on all websites either. There are so many variables and different software out there that few two websites are alike.
Le Mans Master
Joined: Oct 2017
Posts: 5,424
Likes: 2,304
From: Billings Montana. Out in the wild west
Drifting
Joined: Jun 2020
Posts: 1,355
Likes: 396
From: Northwest Ohio
I figured this out.. in iOS 15.4 Safari added "lazy loading" support based on the loading="lazy" attribute being in image tags in the HTML. This forum software puts that loading="lazy" attribute onto the images...I am assuming this is conflicting with the progressive loading scripts that this site utilizes (i.e. you end up with a lazy loaded lazy load 
).
I fixed this by disabling lazy loading in the safari advanced "experimental" settings. This is located here:
Settings -> Safari -> Advanced -> Experimental Features -> Lazy image loading
This should be safe to do and will not hurt anything (other than perhaps slowing down load of sites that fully utilize this attribute). You can always turn it back on.
I think this is a combo of perhaps a "safari" issue but it really may be an issue with the script on this site...and where it may need a tweak to adjust if the browser (particularly iOS) support the lazy loading attribute.
).I fixed this by disabling lazy loading in the safari advanced "experimental" settings. This is located here:
Settings -> Safari -> Advanced -> Experimental Features -> Lazy image loading
This should be safe to do and will not hurt anything (other than perhaps slowing down load of sites that fully utilize this attribute). You can always turn it back on.
I think this is a combo of perhaps a "safari" issue but it really may be an issue with the script on this site...and where it may need a tweak to adjust if the browser (particularly iOS) support the lazy loading attribute.
Race Director
Joined: Jul 2000
Posts: 10,777
Likes: 199
I figured this out.. in iOS 15.4 Safari added "lazy loading" support based on the loading="lazy" attribute being in image tags in the HTML. This forum software puts that loading="lazy" attribute onto the images...I am assuming this is conflicting with the progressive loading scripts that this site utilizes (i.e. you end up with a lazy loaded lazy load ).
I fixed this by disabling lazy loading in the safari advanced "experimental" settings. This is located here:
Settings -> Safari -> Advanced -> Experimental Features -> Lazy image loading
This should be safe to do and will not hurt anything (other than perhaps slowing down load of sites that fully utilize this attribute). You can always turn it back on.
I think this is a combo of perhaps a "safari" issue but it really may be an issue with the script on this site...and where it may need a tweak to adjust if the browser (particularly iOS) support the lazy loading attribute.
).I fixed this by disabling lazy loading in the safari advanced "experimental" settings. This is located here:
Settings -> Safari -> Advanced -> Experimental Features -> Lazy image loading
This should be safe to do and will not hurt anything (other than perhaps slowing down load of sites that fully utilize this attribute). You can always turn it back on.
I think this is a combo of perhaps a "safari" issue but it really may be an issue with the script on this site...and where it may need a tweak to adjust if the browser (particularly iOS) support the lazy loading attribute.
Drifting
Joined: Jun 2020
Posts: 1,355
Likes: 396
From: Northwest Ohio
Apologies, I did not see that this thread started as macOS. It was linked to from a thread about the exact same issue on iOS. It should be the exact same fix, you just get there differently...
Go to:
Safari -> Preferences -> Advanced -> Check the "Show Develop menu in menu bar"
Then from the menu bar go to:
Develop -> Experimental Features -> Uncheck "Lazy image loading"
Go to:
Safari -> Preferences -> Advanced -> Check the "Show Develop menu in menu bar"
Then from the menu bar go to:
Develop -> Experimental Features -> Uncheck "Lazy image loading"
Corvette Stories
The Best of Corvette for Corvette Enthusiasts
How Much Horsepower Every Corvette Engine "LOST" in 1972
Joe Kucinski
Top 10 DOs and DON'Ts for Protecting Your Convertible Top!
Michael S. Palmer
Top 10 Most Explosive Corvettes Ever Made: Power-to-Weight Ratio Ranked!
Joe Kucinski
150 hp to 1,250 hp: Every Corvette Generation Compared by the Specs That Matter
Joe Kucinski
8 Coolest Corvette Pace Cars (and Replicas) of All Time
Verdad Gallardo
Top 10 Corvette Engines RANKED by Peak Torque (70+ Years of Muscle!)
Joe Kucinski
Corvette ZR1X Will Be Pacing the Indy 500, And Could Probably Race, Too!
Verdad Gallardo
Top 10 Corvettes Coming to Mecum Indy 2026!
Brett Foote
Top 10 C9 Corvette MUST-HAVES to Fix These C8 Generation Flaws!
Michael S. Palmer
Racer
Joined: Jan 2022
Posts: 270
Likes: 209
I figured this out.. in iOS 15.4 Safari added "lazy loading" support based on the loading="lazy" attribute being in image tags in the HTML. This forum software puts that loading="lazy" attribute onto the images...I am assuming this is conflicting with the progressive loading scripts that this site utilizes (i.e. you end up with a lazy loaded lazy load ).
I fixed this by disabling lazy loading in the safari advanced "experimental" settings. This is located here:
Settings -> Safari -> Advanced -> Experimental Features -> Lazy image loading
This should be safe to do and will not hurt anything (other than perhaps slowing down load of sites that fully utilize this attribute). You can always turn it back on.
I think this is a combo of perhaps a "safari" issue but it really may be an issue with the script on this site...and where it may need a tweak to adjust if the browser (particularly iOS) support the lazy loading attribute.
).I fixed this by disabling lazy loading in the safari advanced "experimental" settings. This is located here:
Settings -> Safari -> Advanced -> Experimental Features -> Lazy image loading
This should be safe to do and will not hurt anything (other than perhaps slowing down load of sites that fully utilize this attribute). You can always turn it back on.
I think this is a combo of perhaps a "safari" issue but it really may be an issue with the script on this site...and where it may need a tweak to adjust if the browser (particularly iOS) support the lazy loading attribute.
**edit to add that this does seem to work. Chrome was doing the same thing for me.
Race Director
Joined: Jul 2000
Posts: 10,777
Likes: 199
Apologies, I did not see that this thread started as macOS. It was linked to from a thread about the exact same issue on iOS. It should be the exact same fix, you just get there differently...
Go to:
Safari -> Preferences -> Advanced -> Check the "Show Develop menu in menu bar"
Then from the menu bar go to:
Develop -> Experimental Features -> Uncheck "Lazy image loading"
Go to:
Safari -> Preferences -> Advanced -> Check the "Show Develop menu in menu bar"
Then from the menu bar go to:
Develop -> Experimental Features -> Uncheck "Lazy image loading"
IB Staff
Joined: Feb 2009
Posts: 10,575
Likes: 4
I figured this out.. in iOS 15.4 Safari added "lazy loading" support based on the loading="lazy" attribute being in image tags in the HTML. This forum software puts that loading="lazy" attribute onto the images...I am assuming this is conflicting with the progressive loading scripts that this site utilizes (i.e. you end up with a lazy loaded lazy load ).
I fixed this by disabling lazy loading in the safari advanced "experimental" settings. This is located here:
Settings -> Safari -> Advanced -> Experimental Features -> Lazy image loading
This should be safe to do and will not hurt anything (other than perhaps slowing down load of sites that fully utilize this attribute). You can always turn it back on.
I think this is a combo of perhaps a "safari" issue but it really may be an issue with the script on this site...and where it may need a tweak to adjust if the browser (particularly iOS) support the lazy loading attribute.
).I fixed this by disabling lazy loading in the safari advanced "experimental" settings. This is located here:
Settings -> Safari -> Advanced -> Experimental Features -> Lazy image loading
This should be safe to do and will not hurt anything (other than perhaps slowing down load of sites that fully utilize this attribute). You can always turn it back on.
I think this is a combo of perhaps a "safari" issue but it really may be an issue with the script on this site...and where it may need a tweak to adjust if the browser (particularly iOS) support the lazy loading attribute.
Opinion, but I slightly disagree about it being a site issue. Using the "lazy" attribute or class is not uncommon with this feature. So my guess is that other sites using this feature will also have the issue. It's just that not all websites use it.
Drifting
Joined: Jun 2020
Posts: 1,355
Likes: 396
From: Northwest Ohio
Thanks for the info. We'll discuss this finding with the team.
Opinion, but I slightly disagree about it being a site issue. Using the "lazy" attribute or class is not uncommon with this feature. So my guess is that other sites using this feature will also have the issue. It's just that not all websites use it.
Opinion, but I slightly disagree about it being a site issue. Using the "lazy" attribute or class is not uncommon with this feature. So my guess is that other sites using this feature will also have the issue. It's just that not all websites use it.
Anyway, I wish you and your team good luck!
Drifting
Joined: Jun 2020
Posts: 1,355
Likes: 396
From: Northwest Ohio
Thanks! If you mean on iOS, that makes complete sense. Even when you install Chrome (or whatever other browser) on an iOS device, Apple forces that browser to *still* use the Webkit rendering engine from Safari (in other words it may "look" like chrome, have a different UI/feel, but the rendering of the actual pages is STILL essentially Safari). That's why it really stinks when Apple stops providing support for older devices (granted very old devices)...you cannot even load a "modern" browser on them because they are all locked to the same version of Safari Webkit that was last released for that device.
Racer
Joined: Jan 2022
Posts: 270
Likes: 209
Thanks! If you mean on iOS, that makes complete sense. Even when you install Chrome (or whatever other browser) on an iOS device, Apple forces that browser to *still* use the Webkit rendering engine from Safari (in other words it may "look" like chrome, have a different UI/feel, but the rendering of the actual pages is STILL essentially Safari). That's why it really stinks when Apple stops providing support for older devices (granted very old devices)...you cannot even load a "modern" browser on them because they are all locked to the same version of Safari Webkit that was last released for that device.
---------
Joined: Jul 2010
Posts: 1,839
Likes: 20
From: NC
I figured this out.. in iOS 15.4 Safari added "lazy loading" support based on the loading="lazy" attribute being in image tags in the HTML. This forum software puts that loading="lazy" attribute onto the images...I am assuming this is conflicting with the progressive loading scripts that this site utilizes (i.e. you end up with a lazy loaded lazy load ).
I fixed this by disabling lazy loading in the safari advanced "experimental" settings. This is located here:
Settings -> Safari -> Advanced -> Experimental Features -> Lazy image loading
This should be safe to do and will not hurt anything (other than perhaps slowing down load of sites that fully utilize this attribute). You can always turn it back on.
I think this is a combo of perhaps a "safari" issue but it really may be an issue with the script on this site...and where it may need a tweak to adjust if the browser (particularly iOS) support the lazy loading attribute.
).I fixed this by disabling lazy loading in the safari advanced "experimental" settings. This is located here:
Settings -> Safari -> Advanced -> Experimental Features -> Lazy image loading
This should be safe to do and will not hurt anything (other than perhaps slowing down load of sites that fully utilize this attribute). You can always turn it back on.
I think this is a combo of perhaps a "safari" issue but it really may be an issue with the script on this site...and where it may need a tweak to adjust if the browser (particularly iOS) support the lazy loading attribute.
thanks. Works like a charm.
Le Mans Master
Joined: May 2006
Posts: 6,774
Likes: 363
From: Midland TX
I am on MacBook Pro 16" M1 w/ latest Monterrey & Safari - same issue but not 100% of the time. Usually only happens when the first post in a thread includes an image. EITHER double-clicking on the image to open it in a separate window OR just refreshing the page in the browser fixes it.
Burning Brakes
Joined: Oct 2018
Posts: 1,023
Likes: 776
From: Göteborg, Sweden, Europe
2025 C5 of the Year Finalist - Unmodified
2021 C5 of the Year Finalist - Unmodified
2020 C5 of the Year Finalist - Unmodified
No doubt. I'm the industry too...didn't mean to point fingers...it's one of those things where you get backed into a corner where "Apple" or "Microsoft" or "Google" introduces something new (or turns something off!) that doesn't play nice with existing sites. I think in this case it's something with the lazy load JS from vBulletin (?) interacting with that lazy load attribute with Apple 15.4, but I digress as I had to stop myself from debugging further, so that's mostly anecdotal from me. So it's one of those "I'm sure there's a code fix/workaround" but perhaps Apple can be convinced they have an actual bug with that feature...probably worth submitting something to them with evidence, and showing that disabling that functionality makes it work?
Anyway, I wish you and your team good luck!
Anyway, I wish you and your team good luck!