Pro 3.2.3 header builder: scrolling issues if upper sticky bar has height of auto

If the upper bar out of two sticky top bars has a height of auto, scrolling issues arise:

  • on scroll start, the page content doesn’t scroll smoothly but instead jumps right to the top of the window
  • on scroll start, the lower bar won’t stay in place but will also jump to the top and subsequently hide partially

The provided screenshots are taken within Chrome. Firefox shows a quite similar effect.

The additional bug shown here of the upper bar shrinking is described in more detail in this post.

Steps to reproduce:

  1. create a header with two sticky bars at the top
  2. set the upper bar’s height to auto
  3. add some content to the upper bar’s container

Hey Christian,

Thanks for reporting. I have replicated the issue using Pro 3.2.3. I’ll post this in our issue tracker so it will be queued for fixing.

We’re sorry for the inconvenience.

Ok, great! Is there any way for me to track the issue? Will I get a notification or the like when it’s fixed? And is this usually fixed within days, weeks, months, you name it?

Hello Christian,

We use Github. All of the bugs were tracked through Github. Our developers were already aware of the issue. Once they’ll have it fix, we will be rolling out a new release update cycle. Please do watch out for it. You can find the changes in our changelog: https://theme.co/changelog/

Thank you for your understanding.

Hi @ruenel,

thank you for your fast reply!

As I can see it, your github is private and so are the issues, right?

After you mentioned that this bug is already known, I searched for it more thoroughly and found that this is the case since at least September 2018. Makes me wondering about the priority of it being fixed. Do you have any bug bounty program for external developers? Is there a way to get access to the unminified js file as a bare minimum so I can easily fix it myself? Unminified versions shipped with earlier versions of Pro IIRC but I don’t see them anymore.

Hi Christian,

First of all, we are delighted for your offer to donate your time to help us out for the bug fix. It is heartwarming to see our great customers take part in to make our product a better one.

The problem in question seems to be a regression of the changes done for another feature. Honestly, the code of the theme is nothing like the 2018 version so, it might seem like it took that much time to handle but it is not the case actually.

I double-checked our issue tracker and the bug is still in the process of being looked into and not fixed yet. I will tag this thread and inform our development team for your gracious offer.

Thank you.

Hi Christian,

Just letting you know that I’m currently investigating this issue and thanks for the information. But just applying outerHeight() is not working, it may need further testing. Example, if you add a margin on the container where header bar is like 30px both top and bottom, it will add up to the original header bar height causing a clipping.

Example, header bar is 200px, and since the header container inherit header bar, it will be 200px as well, now calling outerHeight() will make the container 200px + 60px and that’s causing overflow or clipping. It may work on some setup but may not on containers that may add more values, but I’m still on it and thanks for sharing :slight_smile:

Thanks!

Hi Christian,

Just letting you know that it’s already fixed on our unreleased version, and thanks for the help. It’s by implementing outerHeight() while subtracting inner paddings.

Thanks!

Thank you all, looking forward to the bug fix being released :+1: :star_struck:

You’re most welcome, Christian.

Hi @rad,

thank you for the detailed information! After thinking about it for a while, I’m not fully convinced that my issues will be fixed with the corresponding release.

You’re only talking about the margin and positioning issue that I shared in thread 71400. Does that mean the issue in this ticket (scrolling with upper sticky bar having a height of auto) is still not fixed, or did you manage that as well?

Regarding the margin and padding issues, I have a feeling that the solution coming will not fully work for me. The detailed setup is like this: top sticky bar with height of auto and padding (0.5em at top and bottom) with two containers inside that have margin (0.5em at top and bottom) applied. This bar has to be fully responsive so the containers will wrap at some point. The addition of bar padding and container margin makes sure that it always looks nice by preserving the same distance to neighboring elements in wrapped and unwrapped state. Using individual bars depending on breakpoints will not work well as I need way more breakpoints than available predefined making it quite some mess to maintain.

Well, maybe I misunderstood you or misinterpreted the effects of your solution and everything is fine though - I’ll wait and see :crossed_fingers: :slight_smile:

Anyway, thanks a lot for all your efforts, keep up with the great work all of you are doing!

Hi Christian,

When an update is released, we provide some information about the bug fixes included in our changelog which you can check:

And thanks for your kind words!

This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.