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

Page redirect warning appears in current tab for links opened in new tab




Tabbed Browser
5 years ago
5 years ago


(Reporter: Silanea, Unassigned)



Firefox Tracking Flags

(Not tracked)




5 years ago
User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:21.0) Gecko/20130212 Firefox/21.0
Build ID: 20130212031120

Steps to reproduce:

With page redirect warnings enabled, opening a link on a website into a new tab causes the warning to be shown in the current tab instead of the new one where it belongs. Opening multiple links into new tabs where several of the newly opened pages redirect has the warning overwritten with only the last redirect shown.

This issue must have been introduced in the last few days. The warnings previously showed up in the newly opened tab.
Care to find a Regression Range?
I cannot reproduce on the build in comment 0.
1. Open google.com
2. Search "cnn"
3. Open first result in a new tab
Actual result: Redirect warning is shown in the right tab.

Silanea, can you please provide some more specific steps to reproduce the problem and some links to test?

Comment 3

5 years ago
How to get the redirect warning to show?  No warning is shown for me at all at google.com or identi.ca (ur1.ca and similar shortening links) if I check the box Preferences → Advanced → General → “Warn me when websites try to redirect or reload the page” with:
* 2013-02-12-03-11-20-mozilla-central-firefox-21.0a1.en-US.linux-x86_64
* 2013-02-18-03-11-06-mozilla-central-firefox-21.0a1.en-US.linux-x86_64
google shouldn't, but www.cnn.com should

Comment 5

5 years ago
WFM with:

Comment 6

5 years ago
I see this in 20.0 Beta with my profile, but cannot get a redirect warning to show with a new profile.  Maybe it shows up because of an extension.

Comment 7

5 years ago
Moving because it seems somewhat similar to bug 678380.
Component: Untriaged → Tabbed Browser


5 years ago
OS: Windows 7 → All


5 years ago
See Also: → bug 873790
You need to log in before you can comment on or make changes to this bug.