STR:

1. Set fission.autostart = true and restart.
2. Visit https://support.google.com/youtube/answer/171780?hl=en and click on "Embed videos and playlists" image to show embedded video.
3. Zoom page to 133%.
4. Take screenshot with "Save visible" or select region.

The video frame contents appears too large in the screenshot and gets cropped. When the page is zoomed out, the frame contents is too small. Does not happen with "Save full page" or fission.autostart = false.

Regression window:
https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=a1a730897df8caf06d617c02468bb8f246bf0a59&tochange=69bbb46eebb13ad8fdda1c0849be0425711ff2be

Regressed by Bug 1720152.

This bug also occurs on Retina displays because they have a device pixel ratio of 2.0.

The frames content doesn't use the correct scaling when taking a screenshot with fission.

Is this bug a duplicate of bug 1729996 where screenshots have black border at some zoom factors?

When I filed that bug, I bisected it to being a regression from graphics bug 1684760 in Firefox 86 and not Fission-specific.

(In reply to Chris Peterson [:cpeterson] from comment #2)

Is this bug a duplicate of bug 1729996 where screenshots have black border at some zoom factors?

When I filed that bug, I bisected it to being a regression from graphics bug 1684760 in Firefox 86 and not Fission-specific.

This bug only occurs when fission is enabled so I don't think this is a duplicated of bug 1729996.

I do think this is a duplicate of bug 1737579 because that one also only occurred with fission enabled.

It occurs only when fission is enabled and when zoomed in or when the device pixel ratio is not 1.

The severity field is not set for this bug.
:jimm, could you have a look please?

For more information, please visit auto_nag documentation.

Is Printing: Output the correct component here for a screenshot?

No, this is probably a "Firefox :: Screenshots" or "Core :: Graphics" bug. Given bug 1720152, this is probably a bug in the CrossProcessPaint code.

Can no longer reproduce on latest Nightly 101.0a1 (2022-04-13), most likely fixed by Bug 1751961.