Google ads break back button

RESOLVED INCOMPLETE

Status

()

Firefox
Untriaged
RESOLVED INCOMPLETE
3 years ago
2 years ago

People

(Reporter: David C, Unassigned)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(1 attachment)

(Reporter)

Description

3 years ago
Created attachment 8581694 [details]
screen_capture.webm

User Agent: Mozilla/5.0 (Windows NT 6.3; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/41.0.2272.101 Safari/537.36

Steps to reproduce:

1) Go to affected site
2) Browse to a page of the site
3) Try and go back clicking the back button

Tested with clean, new profiles in Firefox stable (36.0.4) and nightly (39.0a1/2015-03-23/e730012260a4) with same result. No Flash installed.

I also tested with Firefox 31-35, Chrome 41 and IE 11, which don't show this behavior.

Example affected sites: androidayuda.com, adslzone.net, elotrolado.net, testdevelocidad.es


Actual results:

About 70-80% of the times, back button won't work, that is, it won't load the last page. From my observations I couldn't work out why it's not reproducible 100% of the time. Maybe it has something to do with the different ads Google loads.

If you open the Network panel, you can see a new request to http://googleads.g.doubleclick.net/pagead/ads when you click the back button.

I know the steps to reproduce are a bit fuzzy and the bug somehow doesn't always happen, so I'm attaching a screen capture with the hopes it clarifies something.


Expected results:

Back button should work normally, loading the last page.
Hello David,

Is this bug still active in Firefox 42.0 or Nightly 46.0a1?

I can not reproduce this on Firefox 42.0 or Nightly 46.0a1.

Name 	Firefox
Version 	46.0a1
Build ID 	20151216030229
User Agent 	Mozilla/5.0 (Windows NT 6.3; Win64; x64; rv:46.0) Gecko/20100101 Firefox/46.0

Thank you,

Justin
Flags: needinfo?(m8r-7hl8dk)
Closing this bug due to lack of response from the reporter.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 2 years ago
Flags: needinfo?(m8r-7hl8dk)
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.