When Stylebot extension is enabled in Google Chrome, certain PDFs have a high probability of not displaying.
This is likely due to Stylebot, because of the following factors:
There are no PDF display issues when browsing in incognito.
There are no PDF display issues when all other extensions are on besides for Stylebot.
There are no PDF display issues when Stylebot site access is limited to specific pages.
Go to chrome://extensions/ > Stylebot > Details > Site access > On specific sites > Set to specific sites.
There are PDF display issues when Stylebot extension is on and site access is set to "On all sites".
Certain user actions in this state will cause the PDF to display on the page again:
Zooming in or out on the page will cause the PDF to display.
Rotating the PDF will cause the PDF to display.
Fitting the PDF to "fit to page" will cause the PDF to display.
"Fit to page" is the default setting. Clicking on the icon once will set it to "fit to width".
"Fit to width" will not cause the PDF to display. Clicking on the icon once more will set it to "fit to page".
At this point, the PDF will display, so you'll need to click on the icon twice overall.
The following user actions in this state will not result in getting the PDF to be displayed:
Displaying the Stylebot side panel ("Open Stylebot") will not cause the PDF to be displayed.
Changing the PDF page number ("1/1" on the top) will not cause the PDF to be displayed.
Since the PDF is not displayed, the page number at the top is always "1/1".
Scrolling on this page will not cause the PDF to show.
On refreshing the page:
Refreshing the page will occasionally get the PDF to be displayed without requiring any user actions. Sometimes, when refreshing repeatedly, the PDF will display correctly multiple times in a row. However, other times, when refreshing repeatedly, the PDF will fail to be displayed properly, roughly at worst, nine in ten times. This is true when refreshing with the refresh button in the browser, refreshing with F5, and hard refreshing with Ctrl + Shift + R.
Browser
Browser: Google Chrome Version 90.0.4430.212 (Official Build) (64-bit)
Operating System: Windows 10 Home 19042.985
I first actively noticed this issue May 1, 2021 when I had to look at several PDF documents. This issue may have occurred prior to that date, but it's unlikely that this issue has been occurring for months, because I probably would have noticed this issue sooner. Therefore, this bug was likely introduced around April based on commit history for this project and timeline.
Describe the bug
When Stylebot extension is enabled in Google Chrome, certain PDFs have a high probability of not displaying.
This is likely due to Stylebot, because of the following factors:
Certain user actions in this state will cause the PDF to display on the page again:
The following user actions in this state will not result in getting the PDF to be displayed:
On refreshing the page:
Refreshing the page will occasionally get the PDF to be displayed without requiring any user actions. Sometimes, when refreshing repeatedly, the PDF will display correctly multiple times in a row. However, other times, when refreshing repeatedly, the PDF will fail to be displayed properly, roughly at worst, nine in ten times. This is true when refreshing with the refresh button in the browser, refreshing with F5, and hard refreshing with Ctrl + Shift + R.
Browser
Browser: Google Chrome Version 90.0.4430.212 (Official Build) (64-bit) Operating System: Windows 10 Home 19042.985
To Reproduce
Expected behavior
PDF is displayed correctly every time without requiring user action.
Screenshots
This is what it looks like when the PDF is not displayed correctly:
Additional context
Here are other details regarding this bug:
Here are some more PDF files that also display this issue:
Most PDFs I've encountered have this issue though, so pretty much any PDF will work.
However, I've found that some PDF files display correctly every time without user action:
Timeline
I first actively noticed this issue May 1, 2021 when I had to look at several PDF documents. This issue may have occurred prior to that date, but it's unlikely that this issue has been occurring for months, because I probably would have noticed this issue sooner. Therefore, this bug was likely introduced around April based on commit history for this project and timeline.