722329 - Redirect doesn't allow to open popup window (Redirect via JavaScript doesn't allow to set site permissions)

Status: NEW

(Firefox :: General, defect)

Description

[Nicolas Barbulesco]

Hello,

I encounter a problem in Firefox 3.0.1 and in Firefox 9.0.1. On Windows.

My pref “Warn me when web sites try to redirect or reload the page” is ticked. Firefox' help says : “When this preference is enabled, Firefox will prevent websites from redirecting you to another page, or automatically reloading.” Unfortunately, it does not work in all cases.

I want my bus timetable. I have a Firefox window. I go to http://www.ratp.fr/informer/pdf/horaires/pivot_horaire.php?reseau=busratp&service=THL&ligne=290 .

Expected behaviour :

The popup yellow bar appears. I click on the “Options” “buttenu” — see request bug 688130. I choose the blocked address. I get my bus timetable.

Actual behaviour :

The popup yellow bar appears, and disappears very quickly. I don't have the time to understand what has appeared, let alone to click on “Options”. I land on a page where I don't have any access to my bus timetable. I have been redirected, although I did not allow it. I try again, several times, but with a variant : after I request the address, I press Esc Esc Esc Esc Esc Esc Esc Esc Esc Esc Esc Esc very quickly. At last, I get the popup yellow bar to stay, I click on “Options”, I choose the blocked address, and I get my bus timetable. This is not very accessible — to say the least.

From the W3C, I read the techniques for the guideline “3.5 Toggle automatic content retrieval (P1)” : www.w3.org/TR/UAAG10-TECHS/guidelines.html#tech-configure-content-retrieval :

“Allow configuration so that the user agent only retrieves content on explicit user request.”

See the W3C's User Agent Accessibility Guidelines 1.0 : http://www.w3.org/TR/UAAG10/guidelines.html#tech-time-independent : “2.4 Allow time-independent interaction (P1)”.

Thanks for correcting that.

Nicolas

Comment 1

[:aceman]

Isn't this the same as bug 687300 ?

What happens when you untick “Warn me when web sites try to redirect or reload the page” ? Do you get redirected to the correct page?

Comment 2

[Nicolas Barbulesco]

(In reply to :aceman from comment #1)

> What happens when you untick “Warn me when web sites try to redirect or
> reload the page” ? Do you get redirected to the correct page?

I don't think so.

Comment 3

[:aceman]

I do not understand this now. Regardless of the setting of "Warn me when web sites try to redirect or reload the page" you get redirected to the wrong page?

Comment 4

[Nicolas Barbulesco]

It seems so.

Without the redirect, I would be able to easily use the popup yellow bar as expected.

Comment 5

[:aceman]

Ok, so try to disable Javascript temporarily and visit the site. Does the popup bar stay?

Comment 6

[Nicolas Barbulesco]

With Firefox 9.0.1 with JavaScript temporarily disabled, when I test going to http://www.ratp.fr/informer/pdf/horaires/pivot_horaire.php?reseau=busratp&service=THL&ligne=290 , I get a white page. No yellow bar, no popup window, nothing.

Comment 7

[Ralf Hauser]

see also Bug 951685

Comment 8

[arni2033]

Attachment: testcase 1 (Bug 722329) - pivot_horaire.php (downloaded from the site).html

Info:
1) This bug is "New" (valid; reproducible)   [Win7_64, Nightly 46, 32bit, ID 20160118030338]
2) The yellow bar says "Nightly prevented this site from opening a pop-up window."
   The site tries to open a window and load another link in tab (via JS), but fails to open the window.
   There's special-case for GoogleChrome in the code, so it works correctly on GoogleChrome.
3) This could probably be marked as evangelism bug. But I doubt that it will fix
   thousands of web pages over the Web which expose similar bugs on Firefox.
4) I have an idea that could fix all such cases at once:
 Expectations:
  Location shouldn't change (a yellow prompt about redirect should appear) if a page
  has unanswered permission requests. This should work via pref
 "Warn me when websites try to redirect or reload the page" or some special pref.
5) (4) is covered by bug 687300 (the latter is more "powerful")
   But bug 687300 looks too big and may be Wontfix'ed. In this case, (4) still looks nice.

Comment 9

[Worcester12345]

Similar, but not a duplicate of:
Bug 1390490 - "middle" or command-clicking on link opens new "pop up" window, instead of opening link in new tab