-
Notifications
You must be signed in to change notification settings - Fork 19
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
BI doesn't function properly #32
Comments
Thank you @SpitFire-666 for your feedback 👍 |
I'm seeing something similar but in my case, as soon as I hover over any of the BetterViewer buttons, the image shows up. (Before that, I can see the image briefly, then the blurred background being shown, and then nothing until I hover over the buttons) I did try it in a clean profile and everything worked fine. I have started disabling possible addon conflicts as well, but still narrowing it down on my side. 2022-05-16_13-15-27.mp4Well drat ... I took another guess and disabled Download Manager (S3) and that resolved it for me. (It injects code to create a replica of the old status bar on the bottom of a page to show downloads which is very handy) The problem for me now is that I really need to keep that addon (not a big fan of how FF handles download progress\notification) and that the addon isn't under active development any more. |
Describe the bug
Sorry to spam you! Really looking forward to test driving the addon! I'm getting some odd behaviour where BetterViewer loads but seems to fall over. I can only reproduce the issue on one PC 😑
To Reproduce
Steps to reproduce the behavior:
Expected behavior
BetterViewer should load the image normally. Instead, the background blurry image is shown, but the actual image doesn't show and the image controls do not function:
GIF recording here:
https://imgur.com/a/N65YCd0
Screenshots
https://imgur.com/a/N65YCd0
Desktop (please complete the following information):
Additional context
Since it's just one PC that's having the issue, definitely could be something weird on my end.
The text was updated successfully, but these errors were encountered: