The default bug view has changed. See this FAQ.

redirect to second captcha page never loads

RESOLVED FIXED

Status

()

Firefox
Untriaged
RESOLVED FIXED
5 years ago
5 years ago

People

(Reporter: starletpunk1297, Assigned: jet)

Tracking

({regression})

17 Branch
x86
Mac OS X
regression
Points:
---

Firefox Tracking Flags

(firefox16 unaffected, firefox17+ fixed, firefox18 unaffected, firefox19 unaffected)

Details

(URL)

(Reporter)

Description

5 years ago
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:16.0) Gecko/20100101 Firefox/16.0
Build ID: 20121010144125

Steps to reproduce:

attempted to enter a sweepstakes with the new beta 17.0 version of firefox. there is a button to click to make another window open for the captcha entry page. the page opens but the captcha entry never loads. this only happens in this beta version.


Actual results:

second window opened but did not load captcha information


Expected results:

the second window should open and then the captcha should load, as it does in the 16 version
The URL and the exact steps to reproduce are necessary.
(Reporter)

Comment 2

5 years ago
The problem persists in safe mode with addons disabled.

Updated

5 years ago
Component: Untriaged → General

Comment 3

5 years ago
Where is the link to open a captcha in a 2nd window?

Please, provide clear STR to save our time.
STR:
1) load the given URL
2) click on "login" at the top right
3) use "testcc@mailinator.com" and "123456" to login
4) load the given URL again
5) click on the big "enter" under "walmart"
6) click the "submit" button
7) a CSS "popup" with a captcha should open but it's empty.

I can confirm the issue with Firefox and that it's working in Firefox16.0.1
Component: General → Untriaged

Comment 5

5 years ago
Matthias, thanks for the STR.
But it's only broken in FF17, it works fine in FF18+ (see http://i.imgur.com/6NQSz.jpg), so I guess the regression is already fixed and this bug is a dupe.


good=2012-07-25
bad=2012-07-26
Changelog: http://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=ef20925bc2a5&tochange=20db7c6d82cc
Status: UNCONFIRMED → NEW
status-firefox16: --- → unaffected
status-firefox18: --- → unaffected
status-firefox19: --- → unaffected
tracking-firefox17: --- → ?
Ever confirmed: true
Keywords: regression
Sorry that I forgot to mention that it's already fixed on trunk.
I had no time to dig deeper in this issue, thanks for doing the regression search.
We are at beta1 at the moment ?
There is a good chance that the fix will be in beta2.

Comment 7

5 years ago
Yes, only 17b1 at the moment.

Comment 8

5 years ago
It would be helpful to find a smaller regression range and/or when this was fixed. Anthony - can you help with that?

Jet - I think this bug is in your wheelhouse. Let me know if I'm wrong. Also CC'ing roc just in case.
Assignee: nobody → bugs
status-firefox17: --- → affected
tracking-firefox17: ? → +
Keywords: qawanted, regressionwindow-wanted
QA Contact: anthony.s.hughes
CSS pop-up content shows in 17.0b2 and does not in 17.0b1. I'm guessing something was uplifted that fixed this.

Pushlog between 17b1 and 17b2:
http://hg.mozilla.org/releases/mozilla-beta/pushloghtml?fromchange=6b83222781e3&tochange=2ba4becf6e35
Using the tinderbox builds I think the regression range is between the following changesets.

Last Bad:
http://hg.mozilla.org/releases/mozilla-beta/rev/7ab34cfe4869

First Good:
http://hg.mozilla.org/releases/mozilla-beta/rev/e669a7b1ed5e

Pushlog:
http://hg.mozilla.org/releases/mozilla-beta/pushloghtml?fromchange=7ab34cfe4869&tochange=e669a7b1ed5e

Suspected fixed by bug 786740 - Fix invalidations on out-of-flow frames (roc,r=cwiiis,a=lsblakk)
Keywords: qawanted, regressionwindow-wanted
So it's fixed on 17 now. We can close this bug, then?

Comment 12

5 years ago
Yes, it's a dupe of bug 786740.
(Reporter)

Comment 13

5 years ago
Okay.  So, if the fix is in 17b2, how can I get a copy of it?
Status: NEW → RESOLVED
Last Resolved: 5 years ago
Resolution: --- → FIXED
status-firefox17: affected → fixed
(In reply to starletpunk1297 from comment #13)
> Okay.  So, if the fix is in 17b2, how can I get a copy of it?

I don't know the exact release date for beta2 but it should be soon, Your beta1 build will update to beta2 and the issue should be gone.
Our current plan is to release Firefox 17.0b2 on Monday, October 22nd. If you simply want to test that this is fixed, you can grab the candidate build from here:
ftp://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/17.0b2-candidates/build1/
You need to log in before you can comment on or make changes to this bug.