665964 - The backbutton stops working if an nsISHistoryListener vetoes navigation.

Status: RESOLVED FIXED

(Core :: DOM: Navigation, defect)

Description

[Jeff Muizelaar [:jrmuizel]]

I've seen this twice now. The back button remains inactive even after navigating to different pages. It only seems to affect a single tab. I have no idea how to reproduce it.

Comment 1

[Kyle Huey (Exited; not receiving bugmail, old account, do not use)]

I wonder if this is related to Bug 622315.

Comment 2

[Boris Zbarsky [:bzbarsky]]

Could be....

Comment 3

[Josh Matthews [:jdm]]

I can reproduce this by opening a new tab, starting a page load then cancelling it immediately. No matter where I navigate in that tab from then on, the back button is always disabled.

Comment 4

[Kyle Huey (Exited; not receiving bugmail, old account, do not use)]

I can reproduce that as well.  I'll dig in here.

Comment 5

[Kyle Huey (Exited; not receiving bugmail, old account, do not use)]

This does not seem to be a regression from Bug 662315.  Bisecting now.

Comment 6

[Kyle Huey (Exited; not receiving bugmail, old account, do not use)]

I can only seem to reproduce this sporadically :-(

Comment 7

[Kyle Huey (Exited; not receiving bugmail, old account, do not use)]

I still haven't been able to come up with reliable STR, but I managed to hit this and popped into a debugger and the issue is indeed that mRequestedIndex is not reset.  At this point I'm just going to try to audit the relevant codepaths.

Comment 8

[Asa Dotzler [:asa]]

tracking because if this is widespread, it would be concerning.

Comment 9

[Kyle Huey (Exited; not receiving bugmail, old account, do not use)]

Brief summary:

In bug 622315 we gated navigation on checking nsSHistory::mRequestedIndex to see if there was already a pending navigation.  mRequestedIndex does not always get reset properly, so there are times where we think we're navigating and disable back/forwards when we shouldn't.

Without reliable STR this is going to be difficult to fix.  We can back out the regressing changeset if it comes to that.  This affects 7, so we have some time to figure this out.

Comment 10

[Kyle Huey (Exited; not receiving bugmail, old account, do not use)]

Attachment: Fix at least one bug

If the nsISHistoryListener vetoes we don't set mRequestedIndex.  This can't be hit in stock Firefox, afaict, but an addon could trigger this.

Comment 11

[Boris Zbarsky [:bzbarsky]]

Comment on attachment 544874 [details] [diff] [review]
Fix at least one bug

r=me

Comment 12

[Kyle Huey (Exited; not receiving bugmail, old account, do not use)]

Comment on attachment 544874 [details] [diff] [review]
Fix at least one bug

Drivers, this fixes a particular codepath that addons can trigger in Firefox 7 that will cause forward/backwards to stop working on the tab.

Comment 13

[Kyle Huey (Exited; not receiving bugmail, old account, do not use)]

http://hg.mozilla.org/integration/mozilla-inbound/rev/2ca111e7c2fb

Comment 14

[Kyle Huey (Exited; not receiving bugmail, old account, do not use)]

http://hg.mozilla.org/mozilla-central/rev/2ca111e7c2fb

Comment 15

[Kyle Huey (Exited; not receiving bugmail, old account, do not use)]

http://hg.mozilla.org/releases/mozilla-aurora/rev/ffeea656548b

I'm going to open another bug for the general audit.

Comment 16

[Jeff Muizelaar [:jrmuizel]]

I'm seeing this again on a nightly from 2011-08-09.

Comment 17

[Simona Badau, Desktop QA]

Mozilla/5.0 (Windows NT 5.1; rv:7.0) Gecko/20100101 Firefox/7.0

I tried to verify this fix, but i wasn't able to reproduce this issue with the steps in Comment 3. Can anyone please help me with a test case or with thorough STR in order to get this issue checked on QA side?

Thanks!

Comment 18

[Jeff Muizelaar [:jrmuizel]]

And again with a nightly from 2011-08-31

Comment 19

[Kyle Huey (Exited; not receiving bugmail, old account, do not use)]

Open a new bug please.

Comment 20

[Jeff Muizelaar [:jrmuizel]]

Done. Bug 683886

Comment 21

[u279076]

qa- as we are unable to reproduce the issue on an unpatched build. Can someone who is able to reproduce the bug before please verify this fix?