Hi,

thank you very much for this great module!
We've experienced the problem that the related CSS is not matching in views when using Blazy Grid for example with CSS grid when using https://www.drupal.org/project/views_infinite_scroll as pager.

The infinite scroll module add's an extra wrapper between the .item-list wrapper and the views-rows. So the grid css child selectors are not working anymore (eg: ".medium-block-grid-1 > .grid")

CommentFileSizeAuthor
#3 pager-wrapper-classes.patch1.18 KBjienckebd

Comments

Anybody created an issue. See original summary.

anybody’s picture

Title: Blazy Grid Views Formatter: CSS not loaded » Blazy Grid Views Formatter: incompatible with views_infinite_scroll
Issue summary: View changes

Sorry, we were on the wrong path...

We've experienced the problem that the related CSS is not being loaded in views when using Blazy Grid for example with CSS grid.
The HTML structure is set correctly but not styled by any CSS. We've been trying to use this formatter for the media library view.

The true reason is that https://www.drupal.org/project/views_infinite_scroll changes the structure and the CSS does not match correctly anymore.

The infinite scroll module add's an extra wrapper between the .item-list wrapper and the views-rows. So the grid css child selectors are not working anymore (eg: ".medium-block-grid-1 > .grid")

jienckebd’s picture

StatusFileSize
new1.18 KB

The attached patch fixed it for me.

anybody’s picture

Status: Active » Needs review
jienckebd’s picture

I should have submitted the above patch to the views_infinite_scroll issue queue instead of blazy. And I realized afterwards that I wrote the patch wrong too. I went to submit a follow up patch, and found the issue is already being resolved in views_infinite_scroll issue queue here: https://www.drupal.org/project/views_infinite_scroll/issues/2945524

So I think you may be able to close this one.

anybody’s picture

Status: Needs review » Closed (works as designed)
anybody’s picture

gausarts’s picture

Category: Bug report » Support request

Thanks for tracking down the issue and the followup!