Separate Issue; Your System Details shows;

Installed Plug-ins

Shockwave Flash 18.0 r0 Shockwave Flash 12.0 r0
Having more than one version of a program may cause issues. You must remove the older programs. Then get the current full installer.

Flash: Grab the uninstaller from here: Uninstall Flash Player | Windows Uninstall Flash Player | Mac

Then reinstall the latest version.

Flash Player Version 18.0.0.203
https://www.adobe.com/products/flashplayer/distribution3.html Note: Windows users must download the “Internet Explorer” and “Plugin-based browsers” installers.

Start Firefox in Safe Mode {web Link} by holding down the <Shift>
(Mac Options) key, and then starting Firefox. Is the problem still there?

Thanks -- this probably solved another bothersome glitch, but it didn't phase this problem. Like I said, my husband has the same problem on his Linux Firefox that he updated. It's not on the Linux computer that he has not updated Firefox. So I can only assume it's something in the newest version.

What method are you using to save the comic?

If I enlarge and then right-click > Save Image As... I definitely get a gibberish file name. I have attached a screen shot from right-click > View Image Info showing what I mean.

I get exactly the same name as you for that comic. I get a different name for the regular sized comic, but still 32 characters that look like a hex number (letters a-f and numbers): "7683ea90fb210132ee1c005056a9545d.gif". My laptop still has version 38.05, and the filename is the normal one, "pb150710.gif".

Oh, sorry, didn't actually answer your question -- I save it using the same method as you, right-click and choose Save Image As.

It took me a while to figure out where that short file name was coming from. The server sends it in a Content-Disposition header (screen captures from Firefox 39 and Google Chrome attached). I don't know why Firefox 39 would ignore that header when previous versions did not. Further research required.

I can replicate the problem on my old Maui photo site. For example:

http://www.jeffersonscher.com/photos/Maui07/BlackRock

Below the 640x480 images are a few links:

• Download => Firefox 39 reads the intended filename from the content-disposition header, works normally

• Show in new window (launches larger image in a new tab), then:
   
  • right-click > Save Image As => Firefox 39 does not read the intended filename and instead uses (a portion of) the literal file name
     
  • Ctrl+s (same as Save Page As) => Firefox 39 reads the intended filename from the content-disposition header, works normally

So this seems to be particular to Save Image As. I looked over the list of changes for Firefox 39 and nothing stuck out as related, so I think someone will need to file a new bug.

Do I need to file a bug? I've never done it, but I can probably figure it out.

Found it. This was already reported last week and fixed ... for Firefox 42. I don't know whether it will be fixed for Firefox 40 (due out in about 5 weeks), but that seems very possible. However, until then...

Temporary Workarounds:

For images accessed with a direct link: right-click the link > Save Link As

For other images: view the image "stand-alone" and save the "page" instead of the image (when an image is "stand-alone" those are the same thing). Here's how:

1. right-click > View Image
   or right-click > Ctrl+View Image to open it in a new tab
2. Ctrl+s
   or right-click the black background area > Save Page As
   or "3-bar" menu button > Save Page
   or File menu > Save Page As

(Above is for Windows, for Mac: Ctrl => Cmd)

Bug tracking system: 1180126 – Content-Disposition: inline; filename= doesn't work with Save As.

For more on using the system, see: Bugzilla Etiquette.

Thank you so much! I was dreading having to file it. And that work-around is an extra step, but it works just fine. Appreciate your help!

Hello,

I am glad to hear that your problem has been resolved. If you haven't already, please select the answer that solves the problem. This will help other users with similar problems find the solution more easily.

Thank you for contacting Mozilla Support.

Okay, it didn't really solve the problem, since it's a bug, but I'll mark the answer that points to that fact and that it's been reported and fixed for a future version.