Open Bug 424167 Opened 16 years ago Updated 2 years ago

Option "Warn me when web sites try to redirect or reload the page" does not work correctly. Does not handle more frames.

Categories

(Firefox :: Settings UI, defect)

x86
All
defect

Tracking

()

People

(Reporter: clemens.fuchslocher, Unassigned)

References

(Blocks 1 open bug)

Details

Attachments

(5 files, 1 obsolete file)

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.1.12) Gecko/20080201 Firefox/2.0.0.12
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9b4) Gecko/2008030318 Firefox/3.0b4

It seems that the option "Warn me when web sites try to redirect or reload the page" can only handle one meta refresh element per document. If a document is a frameset or is using iframes and the referenced frames are containing meta refresh elements, then only one refresh gets executed.

Tested with Firefox 3.0b4 from [0] and the nightly build 2008-03-20-04-trunk from [1].

[0] http://www.mozilla.com/en-US/firefox/all-beta.html
[1] http://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/2008/03/2008-03-20-04-trunk/


Reproducible: Always

Steps to Reproduce:
1. Extract testcase.zip.
2. Open testcase/testcase.html.
3. All meta refreshes are executed after the defined time-outs. See testcase-1.png.
4. Enable the option "Warn me when web sites try to redirect or reload the page" under Edit -> Preferences -> Advanced -> General -> Accessibility.
5. Open testcase/testcase.html again.
6. A toolbar is now displayed at the top of the document. See testcase-2.png.
7. Press the allow button.
8. Only one meta refresh is executed immediately. See testcase-3.png.
Attached file testcase.zip
Attached image testcase-1.png
Attached image testcase-3.png (obsolete) —
Attached image testcase-2.png
Attached image testcase-3.png
Attachment #310789 - Attachment is obsolete: true
See also bug 369652.
OS: Linux → All
Version: unspecified → Trunk
Also, this feature don't really do what the user expects.

My credit union has 600 second meta refresh that's used to timeout the session:
<meta HTTP-EQUIV="Refresh" CONTENT="600; URL=/hb/Timeout.asp">

So, if I login with redirect warning on, I immediately see the redirect warning. If I do the logical thing and click "Allow", I'm timed-out immediately.

It'd be cool if instead of doing the redirect IMMEDIATELY, the Allow enabled the meta-refresh timeout to remain in effect... i.e. keep counting the 600 seconds.

This is a cool feature, but it doesn't seem quite ready for prime time. And to make matters worse, there seems to be no documentation or help explaining to end users what exactly this feature does or what it's limitations (meta-refresh only) are.
In my experience it is not just pages with multiple frames that only allow 1 meta refresh.  When you have the "warn me" preference enabled (which is the default in Firefox 3), after the first click of "allow", it will refresh immediately (i.e. not at the appropriate time - that's bug 417770) and then it will never refresh again.  It won't even ask you for permission again.

See attachment simpleRefresh.html.  Does everyone else get the same behaviour?  I could raise a new bug for this but it feels like it may be the same underlying issue as for multiple frames. 

I believe once a user has clicked "allow", the page should continue to allow meta refreshes at least until the user has navigated to a new URL.  Perhaps even for the rest of the session (so if they go back to the same URL later they don't have to click "allow" again).  Or perhaps even remember to allow that URL forever in the user's profile. 


As well as the aforementioned bug 417770, I agree with bug 443254 comment #4.  Also, the original bug there seems to be about a website not working when the "warn me" preference is enabled, which developers may wish to take into consideration when working in this area.  Lastly for possible consideration is bug 440580, although the first comment suggests it that be a non-issue.
Actually the behaviour seems to be dependent on other factors.  If I access simpleRefresh.html from a website (e.g. https://bugzilla.mozilla.org/attachment.cgi?id=329831) then it *does* refresh, but you have to click "allow" every time.  As stated, I believe that after a user has clicked "allow" once, the page should continue to allow meta refreshes at least until the user has navigated to a new URL.

But to produce the behaviour described in my comment #8 (i.e. refresh once but never again), it seems to be necessary to access simpleRefresh.html locally (so do "Save Page As ..." and then open it).

I'm on Windows XP:
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-GB; rv:1.9) Gecko/2008052906 Firefox/3.0
I suspect this redirection warning is somehow conflicting with being asked to update a saved password. It seems I get the redirect question, and if I say cancel, I never get the warning asking if I want to save the updated password.

Because this is several levels deep in my credit union's web site, I can't think how to point you at an example of this.
This is still a problem in Firefox 6. The testcase works as described. Only the second frame refreshes.
It is the same as bug 369652, but this one has testcase, screenshots and more discussion.
Status: UNCONFIRMED → NEW
Ever confirmed: true
Summary: Option "Warn me when web sites try to redirect or reload the page" does not work correctly. → Option "Warn me when web sites try to redirect or reload the page" does not work correctly. Does not handle more frames.
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: