Style differs btw cornerstone and front-end

[nblund]

Hi there.

Please have a look at the two images. I don’t get why there is some whitespace on the front-end whereas everything is as expected in Cornerstone.

Login credentials in secure note.

Thanks.

[tristup]

Hi @nblund,

Thanks for reaching out.
I have checked the Layout and found the output is the same in the Page Builder and in the Browser.

If you are seeing any difference, it might be due to the cache. I would suggest you check once by clearing all types of cache including the Style Cache from Cornerstone > Settings > System > Clear Style Cache and check in the incognito/private mode of the browser.

Hope it helps.
Thanks

[nblund]

Hi again.

I am afraid it is not a cache issue. Could it be a browser issue? I can replicate your finding in Chrome, but not in Safari… What to do, please?

[tristup]

Hi @nblund,

If clearing the cache does not resolve your problem, then it might be an issue related to the browser. Can you please mention the device, browser name and version, and also the operating system you are using, which helps us to replicate the issue at our end?

Thanks

[nblund]

Sure.

Device: MacBook Pro 2018
Browser: Safari version 16.1 (18614.2.9.1.12)
OS: Mac OS Venture 13.0.1

Thanks.

[ruenel]

Hello @nblund,

Be advised that the Product Gallery will use the global WooCommerce setting which you have set in Appearance > Customizer > WooCoommerce > Product Images. It will display up to 600 pixels only. Please have it increased to at least 1000 if you want it bigger.

Best Regards.

[nblund]

Hi again,

Thanks for your patience. Unfortunately that doesn’t solve the issue.
See attached image.
I can’t replicate my earlier assumption that it could be a browser issue.
Would you have any other suggestions?

Login credentials in secure note.

[tristup]

Hi @nblund,

I have checked it again but the issue is not visible to us, even the Online Browser Testing tools are not showing the problem shown in the given screenshot.

I would request you to check the same in a different machine and browser, and if that does not exist, I suggest you consult with a local developer who can inspect and investigate the issue specifically on your machine.

Thanks