'Take Screenshot' on the Guardian website crops images and the amount of cropping depends on the zoom settings.
Categories
(Firefox :: Screenshots, defect, P3)
Tracking
()
People
(Reporter: hobbsjm, Unassigned)
References
Details
(Keywords: regression, Whiteboard: [fidefe-maintenance])
Attachments
(1 file)
377.77 KB,
image/jpeg
|
Details |
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:95.0) Gecko/20100101 Firefox/95.0
Steps to reproduce:
Go to the Guardian website and find an image with overlaid text, such as the building graphic on this page: https://www.theguardian.com/society/2022/jan/12/planners-set-to-approve-52-storey-london-tower-with-only-one-staircase.
Right click on the page and select 'Take Screenshot'.
Hover over the composite image and click on it.
Click either the 'Copy' or 'Download' buttons.
If clicking on the 'Download' button, save the image to a file.
Actual results:
Rather than the full image being copied to the clipboard or saved to a file, a cropped version is copied/saved. The amount of cropping is affected by the current zoom level.
Expected results:
The selected image should be copied/saved in its entirety (and the zoom level should not affect the output).
Comment 1•3 years ago
|
||
The Bugbug bot thinks this bug should belong to the 'Firefox::File Handling' component, and is moving the bug to that component. Please revert this change in case you think the bot is wrong.
Thanks for reporting!
Setting it as NEW as I managed to reproduce this using Firefox Release 95, Beta 96 and Nightly 98.0a1 on macOS 11.6 (Big Sur). The issue is not reproducible on 91.5.0esr.
Found commit message:
Bug 1732358 - Part 5: Add the fission rollout slug to the GRADUATION_SET, r=mythmon
Updated•3 years ago
|
Updated•3 years ago
|
Comment 3•3 years ago
|
||
The problem is actually the "iframe".
If user has DPI scaling enabled for the monitor (most modern notebooks does by default), then taking screenshot of any page with "iframe" will shift the content of the "iframe".
So this affects much much more pages and a lot of users.
Also I'm pretty sure this affects the web-extension API as well, both browser.tabs.captureVisibleTab
and browser.tabs.captureTab
. I've reported those today in a bug 1751961.
Updated•3 years ago
|
Comment 4•3 years ago
|
||
Sam, is there any chance we can get an owner for the Screenshots component? Seems to need some love since Emma left.
Comment 5•3 years ago
|
||
(In reply to Bob Hood from comment #4)
Sam, is there any chance we can get an owner for the Screenshots component? Seems to need some love since Emma left.
I'm the module owner of Screenshots and we are maintaining and actively working on it when time allows. But I think what you are asking for is for someone to give it more time, and that's not something I control.
Updated•3 years ago
|
Updated•3 years ago
|
Updated•3 years ago
|
Comment 6•3 years ago
|
||
Lets have another look at this in triage to see if its something we can fix ahead of the browser component port.
Comment 7•3 years ago
|
||
Possible dupe of 1751961. At minimum we're dependent on a resolution there. That bug doesnt have a priority/severity yet either. I'm going to mark this one as P3/S3 and we'll need to revisit when there are status changes.
Updated•3 years ago
|
Updated•3 years ago
|
Description
•