[BUG FIXED] Can’t resize scaled file:// images
Posted: Fri Sep 25, 2020 4:21 am
Hello all, first time user, so I hope I’m doing this right. I tried searching these forums (manually and with the searchbar) and couldn’t find anything about a suspected bug I found, so I’m posting it here:
I recently noticed an issue where any image file on my drive that’s opened in Firefox (file://), when large enough to be scaled down in the window, cannot be resized to its original size. Clicking on it (with the magnifying-glass cursor) has no effect, as if it’s frozen. I can zoom in and out using Ctrl+/-, but the image itself remains scaled (the “Scaled (xx%)” text in the title bar doesn’t change).
This affects all local image files (JPG, PNG, etc.), and only local image files – online images resize just fine.
I’ve confirmed this is caused by NoScript; the issue manifests when NoScript is the only add-on enabled (all others disabled), yet disappears when NoScript is the only add-on disabled (all others enabled).
This issue manifests in both the latest stable release, v11.0.46, as well as the latest listed dev version, v11.0.45rc5. I tried the recent dev builds, and the issue first appears in v11.0.45rc4; it’s not in v11.0.45rc3.
Please let me know if I’m missing something, or if you need any other info.
I recently noticed an issue where any image file on my drive that’s opened in Firefox (file://), when large enough to be scaled down in the window, cannot be resized to its original size. Clicking on it (with the magnifying-glass cursor) has no effect, as if it’s frozen. I can zoom in and out using Ctrl+/-, but the image itself remains scaled (the “Scaled (xx%)” text in the title bar doesn’t change).
This affects all local image files (JPG, PNG, etc.), and only local image files – online images resize just fine.
I’ve confirmed this is caused by NoScript; the issue manifests when NoScript is the only add-on enabled (all others disabled), yet disappears when NoScript is the only add-on disabled (all others enabled).
This issue manifests in both the latest stable release, v11.0.46, as well as the latest listed dev version, v11.0.45rc5. I tried the recent dev builds, and the issue first appears in v11.0.45rc4; it’s not in v11.0.45rc3.
Please let me know if I’m missing something, or if you need any other info.