Skip Navigation

[Resolved] Bug-Chrome on ThinkPad not displaying Grid / Gallery Block correctly

This is the technical support forum for Toolset - a suite of plugins for developing WordPress sites without writing PHP.

Everyone can read this forum, but only Toolset clients can post in it. Toolset support works 6 days per week, 19 hours per day.

This topic contains 2 replies, has 2 voices.

Last updated by martinE-4 1 year ago.

Assigned support staff: Waqar.


My user has sent me screenshots of Chrome on ThinkPad Windows 10 displaying the Toolset GRID and GALLERY blocks incorrectly — see 3 screenshots: Grid Wrong, Gallery wrong, Correct columns, Chrome version.

Yesterday I reported this on Explorer but since that is no longer supported by Microsoft we don't care. But Chrome should work on all platforms. Chrome on Mac and Asus PC works fine. But current Chrome on ThinkPad Windows 10 does not appear to.

Also connected with the GALLERY Block as I was editing it, I noticed a back-end problem in Safari:
1. Only Full Size image was allowed (major issue)
2. changing the gallery style from Grid to Masonry and then back to Grid did not work in the back-end. If you go from Grid style to Masonry style then to Collage style, then you can get back to Grid style (this is a minor issue)
3. Sometimes toggling the CROP switch in Grid style caused images to no longer display properly cropped. This could be fixed by editing the gallery in the media library and inserting an image and then deleting it again. This forced the gallery to work properly. (minor but irritating issue)

I have attached 5 back-end images of the back-end gallery block problem as well - file labels explain — Gallery-Masonry-correct, Gallery-Grid-cropped-wrong1, Gallery-Grid-cropped-wrong, Gallery Grid After Masonry-wrong.

Many thanks for looking at this. I'm only trying to help Toolset be a better product - that is why I report any bugs I find. Sorry.



Languages: English (English )

Timezone: Asia/Karachi (GMT+05:00)

Hi Martin,

This ticket seems to be a duplicate, so you're welcome to mark it as closed/resolved.



This is a duplicate ticket...