1279955 - Browser will not go back to the previous page on some web pages

Status: RESOLVED DUPLICATE of bug 1279050

(Core :: DOM: Navigation, defect)

Description

[Marty]

User Agent: Mozilla/5.0 (Windows NT 6.1; rv:47.0) Gecko/20100101 Firefox/47.0
Build ID: 20160613030258

Steps to reproduce:

Attempted to go back using the back button to the previous page while using a proxy.


Actual results:

It bypassed the previous page and went to the first page (where the url box is).


Expected results:

It should have restored to the previous page.

Comment 1

[Marty]

To reproduce use a proxy with cookies on, for example:

http://mainprox.com/

In the URL box type in any site such as reddit, click on one of the threads then try to go back with the back button:

http://www.reddit.com/r/firefox/

Instead of going back one page it reverts to the first page of the proxy and the forward button is grayed out.

After testing recent nightlies it began with this build:

http://archive.mozilla.org/pub/firefox/tinderbox-builds/mozilla-central-win32/1465306171/

This was also tested with all addons disabled.

Comment 2

[Marty]

A note on this bug: after testing with a fresh profile the problem did not exist. The cause appeared to be related to two addons: Rewrite http headers and Noscript. First, Rewrite http headers and its config settings need to be deleted. NoScript also adds the following to the "capability.policy.maonoscript.sites" string: "mediasource: moz-extension: moz-safe-about: resource:" This too needs to be deleted or the problem will continue.

Comment 3

[Marty]

The entry in capability.policy.maonoscript.sites is default and returns on reboot. The problem has returned after restart and with all addons disabled. It does work properly in a fresh profile and I am unable to determine what manual config setting change is affecting backing up on certain websites. As noted above the problem surfaced on a June 7 build.

Comment 4

[roxleitan]

20160607062931 	Mozilla/5.0 (Windows NT 6.1; rv:50.0) Gecko/20100101 Firefox/50.0

I have tested the issue on latest FF release 47.0,latest Nightly build 20160615030209 and Nightly build  20160607062931 and could not reproduce it. I have tested with "Rewrite http headers"and "Noscript" add-ons and with add-ons disabled.

Comment 5

[Marty]

With a fresh profile and default config settings it works properly. The bug is related to some config change that I'm unable to determine since I've made several. The build where this first appeared was from June 7th so I will attempt a mozregression.

Comment 6

[Marty]

Did mozregression twice and it was narrowed down to these revisions: 

https://hg.mozilla.org/integration/mozilla-inbound/pushloghtml?fromchange=0ac2f7a4fc731929c4872c147ee98dd03e9acd0a&tochange=eb3278ed4eb3e3924c556ef92ef4763008a537f3

Comment 7

[Marty]

Finally found the change in about:config that was made that caused the bug. If you set "browser.sessionhistory.max_total_viewers" to 0 you should reproduce the bug. It needs to be at default -1.

Comment 8

[Boris Zbarsky [:bzbarsky]]

[Tracking Requested - why for this release]: Seems bad.

Note that you can get 0 bfcached viewers if the previous thing just didn't go into bfcache.  So you probably don't need to mess with about:config at all to reproduce the bug in various cases...

Comment 9

[Dragana Damjanovic [:dragana]]

The fix to 1279050 will probably fix this one too.
I will fix this next week the latest.

Comment 10

[Marcia Knous [:marcia]]

Tracking 50+ since the back functionality is important in browsing.

Comment 11

[Masatoshi Kimura [:emk]]

(In reply to Dragana Damjanovic [:dragana] from comment #9)
> The fix to 1279050 will probably fix this one too.
> I will fix this next week the latest.

Th "next week" (now the previous week) has over. When will this be fixed? If you can't fix this in time, bug 968273 should be backed out due to many serious regressions.

Comment 12

[Dragana Damjanovic [:dragana]]

this will be fix by bug 1279050.

Comment 13

[Marcia Knous [:marcia]]

Removing 50 tracking flag - we will track this in the duplicate bug.

Comment 14

[Andrew Overholt [:overholt]]

Clearing affected for 50 since the dupe is tracked there.