Same here. How can I switch back to 91 on macOS?

Hello,

Update: I've updated to Firefox version 92.0.1 and the screenshot functionality remains unchanged.

Thanks to all who may help.

Hello,

Further information - the web developer tools screenshot capability does work.

Again, my thanks to all who help.

Try to reset about:config => screenshots.browser.component.enabled to false if it is currently true (user set).

EDIT: Did you ever used a screenshot extension or do you have such a extension that is currently disabled as that seems to be about this pref ?

Hello cor-el,

Thank you for your response. I did as you suggested and reset about:config => screenshots.browser.component.enabled to false. Now when I try to take a screenshot, nothings happens, which is preferable to receiving a large X and my screen freezing. I did try using a screenshot extension at one point. I have since deleted it. I have attached a screenshot taken with the developer tools that lists my current about:config settings which relate to screenshots.

I appreciate your help.

You can check for problems with preferences. You can delete possible user.js and numbered prefs-##.js files and rename/remove the prefs.js file to reset all prefs to the default value including prefs set via user.js and prefs that are no longer supported in current Firefox releases.

You can use the button on the "Help -> More Troubleshooting Information" (about:support) page to go to the current Firefox profile folder or use the about:profiles page (Root directory).

• Help -> More Troubleshooting Information -> Profile Folder/Directory:
  Windows: Open Folder; Linux: Open Directory; Mac: Show in Finder
• https://support.mozilla.org/en-US/kb/profiles-where-firefox-stores-user-data

Maybe it is time to create a new profile as a quick test to see if your current profile is causing the problem.

See "Creating a profile":

• https://support.mozilla.org/en-US/kb/profile-manager-create-remove-switch-firefox-profiles

If the new profile works then you can transfer files from a previously used profile to the new profile, but be cautious not to copy corrupted files to avoid carrying over problems.

• https://support.mozilla.org/en-US/kb/recovering-important-data-from-an-old-profile

Hi cor-el,

Thanks again for your response.

I followed your directions to reset all prefs. There was only one pref.js file, which I renamed. I restarted FF and the screenshot functionality still did not work.

I then created a new profile. I restarted FF under the new profile and the screenshot functionality still did not work.

If the screenshot still doesn't work in a new virgin profile then something else like security software could be blocking the screenshot feature.

You can check the Web Console for relevant-looking messages.

• "3-bar" menu button -> Web Developer or Tools -> Browser Tools -> Web Developer Tools
• https://developer.mozilla.org/en-US/docs/Tools/Web_Console

Boot the computer in Windows Safe Mode with network support to see if that has effect.

• https://www.bleepingcomputer.com/tuto.../how-to-start-windows-in-safe-mode/
• https://www.digitalcitizen.life/4-ways-boot-safe-mode-windows-10/

Hi cor-el,

I appreciate your willingness to help me sort this out.

My security software settings have remained the same for quite some time – certainly before the Firefox update when I began to experience this lack of screenshot capability.

I did as you suggested and checked the web console for relevant-looking messages, of which there seemed to be none. And I tried doing so on various internet pages.

Rebooting in safe mode with network support, opening FF and trying to take a screenshot had no effect – the screenshot capability still did not work.

I thank you for your time and suggestions thus far.

Hello,

Since the 93.0 update, the screenshot feature works again.

This is true for the right click slide-out menu and the short cuts/overflow menu.

Thank you cor-el for taking the time to try to help me sort out what may have needed to change on my end.

And thank you to any of the developers who may have been monitoring this thread and who implemented the fix.