Unpleasant header behaviour after update

While masonry items load, the page is shorter. That makes it so no scrollbar displays.

When they load and display, the page is longer, and the scrollbar displays. That pushes the site to the left a little bit.

You could give those pages a minimum height so the scrollbar always displays, but it's a little hacky.

Let me know if you need more info :)

Hello Tom,

Thanks for the quick reply !

I understand, yet my customer doesn't like that at all.

If you have a workable solution I will be happy to implement it.

Else I will use the Elementor Theme Builder for masonry archives - not my favorite solution, I prefer to stick to the theme if I can.

Cheers
Bérangère

It looks like you went the Elementor route. Let me know if you decide to do it with GPP again :)

Hello Tom,

If there is a workable solution with GPP, then I'm quite willing to, implement it !

Elementor is just a fallback route. I prefer to use the theme's templates for the blog.

Cheers

Bérangère

I am having the same shake, flickering issue. Pls see recording.

https://www.youtube.com/watch?v=dR17mjkdBfY

I was not able to solve the problem, tried disabling everything but it's still there. Very very distrubing, it happends with chrome only.

Halil - that looks like a different issue. Can you open a new topic?

Bérangère - what if you do this?:

.masonry-container {
    min-height: 800px;
}

Hello Tom,
It solves the issue but creates another one.

When the archive page has only one row, there is a blank space between the posts and the footer.
https://test.ere-digitale-en-resumes.com/categorie/blog/

Seems to be something I need to fix in the plugin.

One last thing - this poster came up with an interesting solution to a similar issue: https://generatepress.com/forums/topic/blog-margin-shift-left/#post-565993

I tried the solution : it can work if you have a boxed layout. With a full-width layout like mine, it creates a blank left margin on the left :
https://test.ere-digitale-en-resumes.com/categorie/blog/

Thought something like that might happen.

In that case, I'll have to tweak this in GP Premium itself. I've added it as an issue to get fixed in 1.6.3.

Thanks Tom, I will test as soon as 1.6.3 is released !

Hello Tom;
it seems to be solved in 1.7 beta2. Thanks !
Bérangère

Great to hear! Thanks for the update :)