Closed
Bug 529712
Opened 15 years ago
Closed 14 years ago
Offline Mode : Work offline page : Hitting Try again button get the previous visited webpage instead of offline mode message
Categories
(Firefox :: General, defect)
Tracking
()
RESOLVED
INCOMPLETE
People
(Reporter: s_maxime, Unassigned)
Details
(Whiteboard: [CLOSEME 2011-1-30])
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.3a1pre) Gecko/20091118 Minefield/3.7a1pre
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.3a1pre) Gecko/20091118 Minefield/3.7a1pre
When you having the Problem loading page, then clicking on the try again button, the browser give you the previous web page visited instead of problem loading page again.
Reproducible: Always
Steps to Reproduce:
1. Get a webpage
2.File, Select Work Offline
3. Try to open an other webpage
--> You'll get the Problem loading page.
4. Hit Try Again button
--> The previous web page appear. It should be tryin again, then showing again the Problem loading page instead of giving the previous webpage.
Actual Results:
The previous well loaded web page appear.
Expected Results:
It should try again, then showing again the Problem loading page instead of giving the previous webpage.
Comment 2•14 years ago
|
||
Reporter, are you still seeing this issue with Firefox 3.6.13 or later in safe mode? If not, please close. These links can help you in your testing.
http://support.mozilla.com/kb/Safe+Mode
http://support.mozilla.com/kb/Managing+profiles
You can also try to reproduce in Firefox 4 Beta 8 or later, there are many improvements in the new version, http://www.mozilla.com/en-US/firefox/all-beta.html
Whiteboard: [CLOSEME 2011-1-30]
Comment 3•14 years ago
|
||
No reply, INCOMPLETE. Please retest with Firefox 3.6.13 or later and a new profile (http://support.mozilla.com/kb/Managing+profiles). If you continue to see this issue with the newest firefox and a new profile, then please comment on this bug.
Status: UNCONFIRMED → RESOLVED
Closed: 14 years ago
Resolution: --- → INCOMPLETE
You need to log in
before you can comment on or make changes to this bug.
Description
•