Yes, that is the way it is SUPPOSED to work. But even with that off this part of the config.xml file is what causes the problem:
<field name="lazyplaceholder"
type="text"
default="res.cloudinary.com/joomshaper/image/upload/v1582107175/placeholder.svg"
label="COM_SPPAGEBUILDER_LAZY_IMG_PLACEHOLDER"
description="COM_SPPAGEBUILDER_LAZY_IMG_PLACEHOLDER_DESC"
showon="lazyloadimg:1" />
Thaat place holedr is what Safari sees and THAT is what the users get, regardless of what the lazy load is set at.
NOW, here is what is contained in the database table "com_sppagebuilder" in the parameter field AFTER the LAZY LOAD is set to off:
{"production_mode":"0","gmap_api":"","ig_token":"{\"appId\":\"\",\"appSecret\":\"\",\"accessToken\":\"\",\"igId\":\"\"}","updater":"https:\/\/www.joomshaper.com\/updates\/com-sp-page-builder-pro.xml","fontawesome":"1","google_fonts":"0","lazyloadimg":"0","**lazyplaceholder":"https:\/\/res.cloudinary.com\/joomshaper\/image\/upload\/v158210717\/placeholder.svg"**,"disableanimatecss":"0","disablecss":"0","disable_og":"0","fb_app_id":"","disable_tc":"0","joomshaper_email":"[email protected]","joomshaper_license_key":"9b1ba702670dbcaedbe01b9ba2131de9"} {"production_mode":"0","gmap_api":"","ig_token":"{\"appId\":\"\",\"appSecret\":\"\",\"accessToken\":\"\",\"igId\":\"\"}","updater":"https:\/\/www.joomshaper.com\/updates\/com-sp-page-builder-pro.xml","fontawesome":"1","google_fonts":"0","lazyloadimg":"0","lazyplaceholder":"https:\/\/res.cloudinary.com\/joomshaper\/image\/upload\/v158210717\/placeholder.svg","disableanimatecss":"0","disablecss":"0","disable_og":"0","fb_app_id":"","disable_tc":"0","joomshaper_email":"[email protected]","joomshaper_license_key":"9b1ba702670dbcaedbe01b9ba2131de9"}
So the lazy load settings do not seem to have any affect on the settings in the database so certain image layouts are formatted and presented with them still on and in place. All other browsers seem to handle this without problems and it is certainly possible that this is a small set of Safari users with older browsers that this affects. That being said, turning the lazy load parameters completely off should still be an option. Some of the addons in pagebuilder are likely just carried over form version to version without regard to how they handle the lazy loading of images. I have researched this quite a bit and we could have a really lengthy discussion about it. I would jst like to see the old options page returned where the placeholder image AND the lazy loading selection actually worked!