Edge Screenshot Save Behavior

[rcollins-PB]

We have confirmed a regression between Edge v151 and v152. The DevTools command "Capture full-size screenshot" no longer behaves correctly in Edge 152. On Edge 152, manual execution of the command presents a Save As dialog limited to DevTools trace formats (*.json, *.heapsnapshot, etc.) rather than image formats. The issue reproduces on clean installations, domain-joined & non-domain-joined systems, and fresh Edge profiles without extensions. Chrome v152 does not reproduce the issue and correctly offers PNG output (albeit, still prompting with a Save As dialog which previously automatically downloaded/saved). Therefore the issue appears to be specific to Microsoft Edge 152.

These are the available formats:

[leahtu]

Thanks for reporting this. Can you share the exact version from edge://version?

Are you referring to the Capture full size screenshot command from the Command Menu (Ctrl+Shift+P) or something else? I can't reproduce the bug on 152.0.4191.53 with that command. Can you provide repro steps?

[rcollins-PB]

152.0.4191.53 (Official build) (64-bit)

Correct - Capture full size screenshot command from the Command Menu (Ctrl+Shift+P). The only place it does provide a PNG option was when I tried it from the "edge://version/" page. However, any other site I receive the reported behavior.

[leahmsft]

Thank you for the details. This was a Chromium bug tracked by https://issues.chromium.org/issues/540267176 and was fixed on August 7 in https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/8213841. The fix will be available in Edge 153 Stable release on September 10th next week.

[rcollins-PB]

Thanks, but the bug you provided is for "screenshot filename truncation". Will that fix the allowance for saving to an image format? Will it also revert back to the original behavior in v151 of allowing automatic downloads without the Save As prompt?

[leahtu]

Yes, that fixes the format issue. For the regression in the automatic download behavior, it looks like it's already tracked upstream: https://issues.chromium.org/issues/554049257. Hopefully a fix will be available soon!