Firefox unable to save text content in offline mode, subsecuently reports: already loaded and presented can not be read from Inet




6 years ago
6 years ago


(Reporter: alex.vesev, Unassigned)


17 Branch

Firefox Tracking Flags

(Not tracked)




6 years ago
User Agent: Mozilla/5.0 (X11; Ubuntu; Linux i686; rv:17.0) Gecko/17.0 Firefox/17.0
Build ID: 20121120063346

Steps to reproduce:

Full Firefox title from About menu item:
Firefox 17,0 - Mozilla Firefox for Canonical - 1.0

1) Visit page:
2) Enable offline mode. (Firefox menu button -> Web Developer -> Work offline)
3) Try to Save the page (it is pure text file, as I catch) somewhere on your disk.
4) It will fails with message-dialog. The page will not be saved at all.

Actual results:

It will fails with message-dialog:

Download error
/home/user/path/where/to/save - "web page title" could not be saved, because the source file could not be read.
Try again later, or contact the server administrator.

Attempt to view page source via right mouse button click will bring the next:

Document Expired
This document is no longer available.
The requested document is not available in Firefox's cache.As a security precaution, Firefox does not automatically re-request sensitive documents.Click Try Again to re-request the document from the website.

But in fact the page content to be saved is fully available on screen and via copy-paste. It is possible to copy and paste the text into an text editor.

Expected results:

This looks like Firefox totally unable to save already loaded _pure_ text pages in offline mode.

Related bug:

Firefox _partially_ unable in offline mode to silently save already loaded pages. Instead it will bring up 20-30+ dialogs about inaccessibility of JavaScrips and similar things do not located inside the page body. Why to try to save them from Internet, explicitly beeng in offline mode.

The page may _not_be_saved_at_all_, if I will correctly shutdown my computer instead of pressing 20-30-60+ times on OK button on every error message dialog.

Rarely, this behaviour may lead to user downloaded _data_loss_. Example: computer was suspended for weekends, then user wake it back, deside to save page, already loaded two days ago. The page content and code exist inside user's computer, inside "opened Firefox windows", but it was deleted from a server while suspending among weekends. The wanted data will be lost for a user.

P.S. While being connected to Internet via mobile phone in rural districts it tooks 5-7 minutes to load some pages. Is some times not possible to do it subsecuently twice (servers often will drop low speed connection now days). Also traffic price is too high.

Excuse me, please, if grammar mistakes ocurs. I have tried my best, but English is not my native, nor profession. Excuse me.

Best regards.
I couldn't reproduce the issue on the latest Nightly (I can save the file without problems)

User Agent: Mozilla/5.0 (X11; Linux i686; rv:20.0) Gecko/20121203 Firefox/20.0
Build ID: 20121203030801 

Could you please try the following :

1) try this with a clean profile:

2) running in Safe mode:
I can reproduce this issue with the latest Nightly.

User Agent: Mozilla/5.0 (X11; Linux i686; rv:20.0) Gecko/20121203 Firefox/20.0
Build ID: 20121203030801
Ever confirmed: true


6 years ago
Component: Untriaged → Location Bar


6 years ago
Component: Location Bar → Untriaged
I'm sorry for comment 2, I was referring to a different bug. Comment 1 is the valid one.

Comment 4

6 years ago
Thank you for your job.

It seems it's related to my extensions set. I have some, against spam and tracking.

Today I'm too can't reproduce main issue (save pure text page) in both modes - safe and with all bells and whistles.

The rest is not reproducible in safe mode.

Now I'm trying to path through quest with extensions - As I'll get valuable results, I'll post information in a forum concerning an extension, or here - if Firefox related.

Best regards
Alv, I'm glad to help! Good luck and best regards!
Last Resolved: 6 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.