512310 - [HTML5] Warning bar with the "Allow" button that prevents page auto reloading/redirecting broken

Status: RESOLVED WORKSFORME

(Core :: DOM: HTML Parser, defect, P2)

Description

[trg16]

User-Agent:       Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.2a2pre) Gecko/20090824 Namoroka/3.6a2pre
Build Identifier: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.2a2pre) Gecko/20090824 Namoroka/3.6a2pre

If I have set accessibility.blockautorefresh to true in about:config or go to preferences/options => advanced tab => general => tick "Warn me when web sites try to redirect or reload the page" , when visiting a site that auto reloads, or in this same forum when you post and it redirects to the thread:

1) Firefox displays a toolbar notification below the tab bar, stating page is trying to redirect you and a button on the right side "Allow". This toolbar (or tooltip) in blank (white bar).

2) When you click blindly where the button should be, after you release the mouse button the toolbar appears and redirects you as it should do.

Check the scroll bar at the right, it's also cut off on the screenshots below...

http://tinyurl.com/mc7enl
http://tinyurl.com/n3gxoy

Reproducible: Always

Steps to Reproduce:
1. Set accessibility.blockautorefresh to true in about:config or go to preferences/options => advanced tab => general => tick "Warn me when web sites try to redirect or reload the page"
2. Visit a site that auto reloads
Actual Results:  
Firefox displays a blank toolbar notification below the tab bar.

If you click the space where the "Allow" button should be, you are redirected as it should do.

Expected Results:  
Firefox should display a toolbar notification below the tab bar, stating page is trying to redirect you and a button on the right side "Allow".

Comment 1

[u88484]

Could you provide the links to the pages that want to redirect and would show the bar?

Or a minimized test case would be great!

Comment 2

[trg16]

Try http://www.terra.com.br  this page auto reloads from time to time. Just enter it and you'll notice the space where the bar should be (check the top of the scroll bar).

About the test case, sorry, have no idea how to do it...

Comment 3

[u88484]

Attachment: testcase

Here is a testcase you can try and let us know if you see the same issue.

Just an FYI, I'm at work without Firefox hence the reason for me not being able to try and reproduce this myself right now.

Comment 4

[trg16]

Yes same issue.

When you click where the "Allow" button should be (on the right side of the bar) the bar appears (when you release the mouse button) and it completes the action...

I've posted this bug on the branch/trunk thread at the forums, but got no reply yet, things are slow over there...

Comment 5

[u88484]

Confirming on latest trunk.  Not sure if the HTML5 parser will be defaulted on in 3.6 so requesting blocking just in case.

Comment 6

[u88484]

Attachment: Screenshot

Comment 7

[u88484]

A major place this happens is within gmail.  Clicking on a link in an email causes a new tab to open, no content and just the grey bar shown.  No errors in the console.

Comment 8

[trg16]

For me in gmail, when I click on a link with the wheel mouse button to open in a new tab, there's no grey bar, it's white and because the whole page is white (waiting for user to click allow) it appears to be an error in the page, because it's all white and no contrast...

Comment 9

[u88484]

(In reply to comment #8)
> For me in gmail, when I click on a link with the wheel mouse button to open in
> a new tab, there's no grey bar, it's white and because the whole page is white
> (waiting for user to click allow) it appears to be an error in the page,
> because it's all white and no contrast...
Probably a difference between Mac and Vista.  BTW, the pop-up blocked bar does show correctly.  Will try the about your rights bar and geolocation bar tonight.

Comment 10

[u88484]

Pop-up blocked, know your rights, remember password prompt, website wants to store on your computer, missing plugin, reported web forgery and the geolocation notification bars work correctly.  I don't think there are any other notification bars so only one is broken.

Comment 11

[u88484]

Attachment: Test case 2

This test case shows that if another notification bar is loaded after, the auto direction notification bar displays correctly after dismissing the pop-up blocked bar.

Comment 12

[trg16]

Your test works. But only in the same tab/bar. If you open a new one, it's blank again.

Comment 13

[u88484]

(In reply to comment #12)
> Your test works. But only in the same tab/bar. If you open a new one, it's
> blank again.

I don't understand.  The test case opens in the same window if you click the link above in the attachments section.  If you ctrl+click the link, then it opens in a new tab and the bug is shown and test case 2 works properly both ways.

Maybe the pop-up is trying to open in a new tab but I have everything forced to open in tabs.

Comment 14

[Johnny Stenback (:jst)]

Reassigning to Henri, and not blocking as this is only an issue when the HTML5 parser is enabled (which won't be the default for 3.6). If there's an easy fix for this that's safe to take for 3.6, I'd gladly consider it, but I don't think this should block the release.

Comment 15

[u88484]

This now WFM.  How about you brassen?

Comment 16

[trg16]

I need to find other site to test. http://www.terra.com.br/ has changed their behavior and Firefox 3.5.5 and Namoroka nightly does not detect their auto reloading anymore (I used this feature to stop sites from auto reloading).

Comment 17

[u88484]

(In reply to comment #16)
> I need to find other site to test. http://www.terra.com.br/ has changed their
> behavior and Firefox 3.5.5 and Namoroka nightly does not detect their auto
> reloading anymore (I used this feature to stop sites from auto reloading).

You can try the test cases here, click on a link in a gmail message, make a post on mozillazine, cnn.com usually has a redirect.

Comment 18

[trg16]

Thank you for the tips. Yes, appears to be fixed.

Comment 19

[u88484]

I'm not sure which one of the recently landed HTML5 patches fixed this so I'm just going to mark this as WFM.

These are the three recent Core:Parser bugs that landed recently.

Bug 483015, bug 500616 and bug 525229