Sidebar not scrollable anymore with Giscus comment presented at after body.

[LumenYoung]

Describe the bug

As I described in the title. I find that when 1) the left sidebar (possibly right sidebar as well, but haven't test it) has content exceeding the current viewable area and 2) when the giscus comment area presents. We lost the ability to scroll on the left side bar.

To Reproduce
Steps to reproduce the behavior:

1. extend your sidebar so that it doesn't fit one page
2. enable the comment
3. try to scroll, either on the main area or on the sidebar
4. See that the side bar stops moving even it is not depleted yet.

Expected behavior

I would expect either

1. if the main content is depleted, the sidebar should start scrolling down (which was the case when no giscus widget has been loaded yet.
2. or if I place my cursor on the sidebar or click on that area, the focus should shift to the area and scroll that part.

Screenshots and Source
I can provide upon request.

You can visit my site www.lumeny.io for a look at the problem. A fun finding is that the sidebar is in a short period of time scrollable before the giscus component is loaded (feel free to try on my site). My quartz codebase is at here.

Desktop (please complete the following information):

• Quartz Version: v4.4

Additional context
Thanks for this amazing work! I can't think of blogging to be sooo rewarding if not with quartz.

[saberzero1]

Thanks for reporting. I'll investigate tomorrow.

[LumenYoung]

Thanks! I'll be looking forward to see it fixed!

[saberzero1]

Thanks! I'll be looking forward to see it fixed!

Hey, I have posted a potential fix, can you check if #1574 fixes your issue?

[LumenYoung]

Hi @saberzero1, thanks for the prompt fix.

I manually applied #1574 and it works! Now my site is working properly with the giscus!

Thanks for the help and I'll close this issue.

[saberzero1]

Hey @LumenYoung, I'm glad it fixes your issue.

I'm going to reopen this issue until the proposed fix has been merged into Quartz for all users to prevent confusion for others running into this issue.