On Tuesday November 28th from 9:00AM PT - 12PM PT (5:00PM UTC - 8PM UTC), we will be performing system maintenance on support.mozilla.org. During the maintenance period, users will not be able to sign in to the website, and all users signed in at the start of the maintenance period will be signed out.

Αυτός ο ιστότοπος θα έχει περιορισμένη λειτουργικότητα, όσο εκτελούμε εργασίες συντήρησης για να βελτιώσουμε την εμπειρία σας. Αν ένα άρθρο δεν επιλύει το ζήτημά σας και θέλετε να κάνετε μια ερώτηση, η κοινότητα υποστήριξής μας είναι έτοιμη να σας βοηθήσει στο Twitter (@FirefoxSupport) και στο Reddit (/r/firefox).

Αναζήτηση στην υποστήριξη

Προσοχή στις απάτες! Δεν θα σας ζητήσουμε ποτέ να καλέσετε ή να στείλετε μήνυμα σε κάποιον αριθμό τηλεφώνου ή να μοιραστείτε προσωπικά δεδομένα. Αναφέρετε τυχόν ύποπτη δραστηριότητα μέσω της επιλογής «Αναφορά κατάχρησης».

Learn More

Screenshot produces black image for google maps.

  • 7 απαντήσεις
  • 3 έχουν αυτό το πρόβλημα
  • 8 προβολές
  • Τελευταία απάντηση από ds_gregg

more options

A few months ago google screenshot started to produce black images when attempting to capture google maps. At the time I had another almost identical pc for which screenshot still worked. I'm running Win 10.

Windows screencapture works but firefox screenshot does not.

What happened?

I doubt it's a graphics hardware thing.

A few months ago google screenshot started to produce black images when attempting to capture google maps. At the time I had another almost identical pc for which screenshot still worked. I'm running Win 10. Windows screencapture works but firefox screenshot does not. What happened? I doubt it's a graphics hardware thing.

Όλες οι απαντήσεις (7)

more options

Hmm, I see that too (on https://www.google.com/maps/ ).

A few versions ago, Firefox changed the way it captures screenshots, but my add-on for screenshots which uses the older method seems to have the same issue, so maybe it's not specific to the screenshot function but is related to the use of an HTML canvas for the map.

Hmm, but Bing Maps also uses an HTML canvas and screenshots seem to work there... https://www.bing.com/maps?where1=2%20Lincoln%20Memorial%20Circle%20NW,%20Washington,%20DC%2020037

So maybe it is specific to Google Maps. Do you want to file a bug report? There are two options:

more options

Works for me on Release (91) and Nightly (93) on Linux.

You can create a new profile as a quick test to see if your current profile is causing the problem.

See "Creating a profile":

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.

Τροποποιήθηκε στις από το χρήστη cor-el

more options

Thanks for the replies. My gut tells me it's a firefox screenshot bug so I guess I'll file a bug report. No one seems to know the root cause of this so maybe someone will care to look into it.

more options

You can check the Web Console (Tools -> Web Developer) for relevant messages.

more options

There are no answers from Firefox here as to why I now get a black screenshot from Google Maps and Win10 since updating Firefox. It used to work fine, why mess with things when they used to work OK? Do I try a new update or revert (if possible) to an older version?

more options

Hi Lance, the code patch to fix this problem (bug 1661869) was finished about two weeks ago, but that was too late for today's release of Firefox 93, so it will be included in Firefox 94 (currently in beta testing, scheduled to be released next month).

For the time being, you can use the built-in Windows features. For example, when you tap the PrtScn button on your keyboard, Windows will capture the entire display to the clipboard so you can paste it into Paint or your preferred image editors. Alt+PrtScn captures the active window. Or check out the Snipping tool: https://support.microsoft.com/en-us/windows/open-snipping-tool-and-take-a-screenshot-a35ac9ff-4a58-24c9-3253-f12bac9f9d44

more options

Thanks for the update. So they recognize it as a bug AND fixed it. Score one for the firefox team.  :)