If you think a bug might affect users in the 57 release, please set the correct tracking and status flags for Release Management.

Cannot save pages from New York Times

UNCONFIRMED
Unassigned

Status

()

Firefox
General
UNCONFIRMED
6 years ago
6 years ago

People

(Reporter: Luis Escobar, Unassigned)

Tracking

8 Branch
x86_64
Windows 7
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [testday-20120203])

Attachments

(1 attachment)

(Reporter)

Description

6 years ago
Created attachment 585217 [details]
FirefoxError.bmp

User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:8.0) Gecko/20100101 Firefox/8.0
Build ID: 20111104165243

Steps to reproduce:

I tried to save an article from the New York Times. Clicked on File, Save Page As...


Actual results:

The article appears to be starting to download, but instead I get a "Download Error" message that says: 
C:\Users\Luis\Desktop\NYT Test-files\273680042.js could not be saved, because the source file could not be read. Try again later, or contact the server administrator."


Expected results:

I should have been able to save the article to my computer, as I have done for years. At first I thought that the NY Times had implemented a widget to block downloading pages. However, I am able to save articles without a problem using MS-IE, Safari, and Chrome.

Comment 1

6 years ago
I can't reproduce this bug using Windows 7 and Mozilla/5.0 (Windows NT 6.1; rv:11.0) Gecko/20100101 Firefox/11.0
Cant reproduce this on ubuntu with beta and nightly

Mozilla/5.0 (X11; Linux x86_64; rv:11.0) Gecko/20100101 Firefox/11.0
Mozilla/5.0 (X11; Linux x86_64; rv:13.0a1) Gecko/20120203 Firefox/13.0a1

Updated

6 years ago
Whiteboard: [20121203 testday]

Updated

6 years ago
Whiteboard: [20121203 testday] → [testday-20120203]

Comment 3

6 years ago
Good day Luis, i cant reproduce this under openSUSE 12.1, KDE 4.7.2 using Mozilla/5.0 (X11; Linux i686; rv:12.0a2) Gecko/20120211 Firefox/12.0a2. 

I think its time to upgrade the browser to a newer version.
You need to log in before you can comment on or make changes to this bug.