Closed Bug 1123403 Opened 10 years ago Closed 10 years ago

When a website opens a new tab with ads, after closing this tab the "back" button is no longer active

Categories

(Firefox for Android Graveyard :: General, defect)

36 Branch
ARM
Android
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: jan.manthay, Unassigned)

Details

Attachments

(1 file)

Attached image no active back button
It may sound a little confusing, but I try my best. This is what happens: I open a webpage. I click on a link on this webpage. The webpage opens a new page with ads, this tab has the focus. I close this tab. I can now see the site of which I have clicked the link. But now the "back" button is no more active, it is greyed out. What happens now depends on the Fx version: On Beta 36 I can press the android-back-button, but instead of going back, the android-homescreen opens, and Firefox disapears. Thats how I recognised this problem. On Aurora 37, when I press the android-back-button it DOES go back. But even here the fx-back-button is greyed out. This is on the classic smartphone-theme, but also on the new tablet-theme. I can give a way to reproduce this most of the time, but it takes a bit of preperations. Open this page: http://www.echo-online.de/region/odenwaldkreis/ Choose "Desktop Version" Open any of the articels on the left pane. Firefox (often, but not always) asks if it should open a pop up. Allow this. Close everything. Delete the cookies, but not the site preferences. Load http://www.echo-online.de/region/odenwaldkreis/ again. Open an article. Now a new tab with ads should open. Close this Tab. Now the problem should be visible. I think it was on my site on about 90%, maybe it depends on the ads. So maybe you must try this 2-3 times. (delete cookies etc.) This happens on multiple sites, but this one was the only one where I could reproduce it more or less relieable. This only happens since 36 Beta, 35 Beta was fine.
Thanks for reporting! I recently fixed bug 1124190, which may be the root of this issue. It is currently in Nightly and will likely be in tomorrow's Aurora (it should be in the next iteration of Beta too). Can you still reproduce the issue using one of these ^ builds?
Flags: needinfo?(jan.manthay)
I did not see this for a while now in aurora or beta, looks ok now.
Flags: needinfo?(jan.manthay)
Status: UNCONFIRMED → RESOLVED
Closed: 10 years ago
Resolution: --- → WORKSFORME
Product: Firefox for Android → Firefox for Android Graveyard
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: