-
Notifications
You must be signed in to change notification settings - Fork 318
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Partial Page Renderer Issue #273
Comments
Partial Page Rendering only renders a partial number of the pages at a time, not literally partial pages. So if rendering is stopping halfway through a page, it's probably a markup issue. Also the number of pages you are deep in your brew will not effect how partial page rendering works, that's the whole point. It figures out which page you are looking at, and only renders the content for the current, the one before and the one after, updating as you scroll. |
Hi, I am having the same problem. I have roughly a 98-page homebrew that I would like to share with other people via the share link, but the rendering makes it so that on certain pages as soon as you scroll down the entire page is gone, replaced by a scroll wheel. How can I fix this so that I can share my brew with people? |
Closing since we have made many related improvements since this was posted, and we can no longer reproduce the issue. If you are still experiencing this issue, feel free to reopen and provide information, @Tsurumah |
Not sure if working as intended, but the Partial Page Renderer renders, literally, a partial page. If you scroll down, you can only see--at least, on my few computers--1/2 to 3/4 of the page, generally cutting off the bottom quarter to half.
Could also be on my end, too, I suppose.
Is there a way to disable the Partial Page Renderer client side, or increase the number of pages that are rendered, around the visible page, client side, of course. First 20-some-odd pages renders fine, however, with no issues, and everything else comes up fine--just makes it difficult to judge distances on images and such.
The text was updated successfully, but these errors were encountered: