has something changed on nightly that would prevent me from saving images?

Hi,

Do you see the Save Image As option?

I can't easily reproduce it, but you are always welcome to file a bug (optionally, add the nightly-community keyword).

hi denys, yes the option is there as normal

Any potential macOS 27 wrinkle or you're running still the same OS version as when it was working?

Seems happy on 15.8 for me, but there are definitely some new permission woes on every single new major OS release:( If reproducing using a clean new Profile as well it might be worth investigating.

Would you be able to run mozregression over a couple of versions to confirm there's a "good" vs. "bad" range for you? tysvm

(Also please restart your Mac for good measure, or if you're able to quickly spin up a new macOS User Profile from System Settings › Users & Groups and launch it from there — to eliminate a macOS bug, that would also be tremendously helpful! Thanks.)

Any potential macOS 27 wrinkle or you're running still the same OS version as when it was working?

hello jbr, i am running the same system, nothing was changed there. I can save images on the brave browser as normal so it makes me think it's not a mac os bug, i did a restart but nothing changed with that.

Hi

Please appreciate that the Nightly build is very much "under construction" and may have one or two unresolved issues. You may wish to file a bug to make sure it is flagged up to the right people. This support article should help:

https://support.mozilla.org/en-US/kb/file-bug-report-or-feature-request-mozilla

hello paul, thanks but 'filing a bug report' does not look easy at all!

Which step from the screen recording earlier does not work for you? The menu item does nothing, or the file picker is shown but nothing saved, or the picker closes and no download dropdown / toolbar button activates, etc. …?

Can you also try some reasonably random yet reproducible image, like a photo from some wiki article?

If you launch a fresh testing profile (from Profiles menu) does it exhibit the same?

hi jbr, creating a new profile doesn't change anything, yes tried various random images, when i click 'save image as' nothing at all responds or downloads, thanks

So not even the directory panel from system is raised?

If you reproduce on a new profile, and you've updated to current Nightly, please file a bug.

It would help to have a Browser Console open firefox-source-docs.mozilla.org/devtools-user/browser_console/ when clicking on the menu item, to see if anything gets logged in there, and also if your were able to run the mozilla.github.io/mozregression/ tool mentioned earlier (it has a Mac app) to help point to an exact build where this changed for you? (I can post some instructions, but in this case you can just leave all the mozregression inputs to their defaults and only select the date range as e.g. 2026-08-01 as good and 2026-09-25 as bad and let it launch the individual builds for you to confirm "works" or "broken" one after another, to help point to the day and changeset that made the difference on your system — that would be amazing. Thanks!)

jbr, correct, no directory panel is raised, i have tried using the console and the following error messages do show up for some of the save image attempts, but not every time....

NS_ERROR_FAILURE: Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIFilePicker.displayDirectory]

   promiseTargetFile chrome://global/content/contentAreaUtils.js:796

NS_ERROR_FAILURE: Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIFilePicker.displayDirectory]

   promiseTargetFile chrome://global/content/contentAreaUtils.js:796

NS_ERROR_FAILURE: Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIFilePicker.displayDirectory]

   promiseTargetFile chrome://global/content/contentAreaUtils.js:796

Interesting, thanks!

I see some screenshot test failures that however only started on Sept. 25 so that doesn't align with "last few days" before that, and now wondering how a Save as… and screenshot code path can overlap.

For the contentAreaUtils there were some rather distant changes (mostly for PDF and local file:// differentiation re. file pickers) on Sep 10, 2026 for cancelled ones and Aug 25, 2026 for local ones. It would really help to run a mozregression around these dates, and file a bug with the details.

(If it seems the screenshot functionality and content image saving flaws are related, please also check the console for what happens when you're taking a screenshot — and if bisecting, please do verify both the features to see if they fail on the same day/build — thanks!)