back button (menu, shortcut) doesn't go back

RESOLVED INCOMPLETE

Status

()

Core
Document Navigation
RESOLVED INCOMPLETE
8 years ago
7 years ago

People

(Reporter: shaver, Assigned: Ehsan)

Tracking

({qawanted})

Trunk
x86_64
Windows 7
qawanted
Points:
---

Firefox Tracking Flags

(blocking2.0 betaN+)

Details

(Whiteboard: [softblocker][may be a dupe of bug 597315])

Chasing a reply-to link in Twitter web UI, can't go back.  Tried back button on my mouse, then UI back button, then alt-left, then history -> back.  Nada!

Back button in toolbar isn't disabled, responds to hover.

Seems to work in other tabs (all the above mechanisms), but switching *back* to the twitter tab gives me: 

Error: [Exception... "Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIWebNavigation.canGoBack]"  nsresult: "0x80004005 (NS_ERROR_FAILURE)"  location: "JS frame :: chrome://browser/content/browser.js :: UpdateBackForwardCommands :: line 3604"  data: no]
Source File: chrome://browser/content/tabbrowser.xml
Line: 283

Nonetheless, the back button changes to enabled if I'm switching from a tab where it wasn't.  Somewhere in my testing just now I also generated: 

Error: aTab is null
Source File: chrome://browser/content/tabbrowser.xml
Line: 1669

Mozilla/5.0 (Windows; Windows NT 6.1; WOW64; rv:2.0b3pre) Gecko/20100722 Minefield/4.0b3pre

add-ons: Weave (disabled due to compat, though I said it works OK? -- different bug!), firebug, mass-password-reset, compat reporter

My current tabs are:

http://twitter.com/shaver/status/19334963262

http://www.youtube.com/watch?v=7Xc2lQdGFQ0

http://www.h-online.com/security/features/CSI-Internet-Alarm-at-the-pizza-service-1019940.html

http://bit.ly/?v=3&u=http%3A%2F%2Fwww.h-online.com%2Fsecurity%2Ffeatures%2FCSI-Internet-Alarm-at-the-pizza-service-1019940.html&t=CSI%3AInternet%20-%20Alarm%20at%20the%20pizza%20service%20-%20The%20H%20Security%3A%20News%20and%20Features&s=

about:addons

http://www.cleanairkinginc.com/

https://bugzilla.mozilla.org/enter_bug.cgi?product=Firefox
Hardware: x86 → x86_64
I was going to try to preserve this process in case people wanted to find out more, but I got all excited about grafxbot and restarted to install it. :-/

Blame jgriffin, I guess!
Blocking+, multiple reports confirming this on input.m.o.
blocking2.0: ? → betaN+
Can this be reproduced reliably?
Keywords: qawanted
Does anyone still see this at all?
I think I saw it in the input.m.o scroll today, but it might have been talking about something else.  I haven't seen it since July myself.
(Assignee)

Comment 6

8 years ago
This is docshell, really.
Component: Tabbed Browser → Document Navigation
Product: Firefox → Core
QA Contact: tabbed.browser → docshell
(Assignee)

Comment 8

8 years ago
Well, actually I was wrong in comment 7.  GetIndex can never fail.  Maybe this? <http://mxr.mozilla.org/mozilla-central/source/docshell/base/nsDocShell.cpp#3572>
As in, failure to get a session history at all?  Possible, but seems pretty unlikely.
(Assignee)

Comment 10

8 years ago
(In reply to comment #9)
> As in, failure to get a session history at all?  Possible, but seems pretty
> unlikely.

Agreed, but that's the only explanation I could come up with looking at the code... :/

Updated

8 years ago
Assignee: nobody → ehsan
(Assignee)

Comment 11

8 years ago
Bug 597315 _may_ be relevant here.
It's clear that this bug as originally filed is different from bug 597774, but they might look similar.

Updated

7 years ago
Whiteboard: [softblocker]
(Assignee)

Updated

7 years ago
Whiteboard: [softblocker] → [softblocker][may be a dupe of bug 597315]
(Assignee)

Comment 13

7 years ago
Shaver, do you remember if you have opened the twitter tab in comment 0 using Undo Close Tab (or Undo Close Window) by any chance?  Or have you restored your session after a restart?
I'm flattered by your opinion of my memory, but no, I don't recall.
(Assignee)

Comment 15

7 years ago
I think without more information, all we can do here is to resolve it as INCOMPLETE.
concur.
Status: NEW → RESOLVED
Last Resolved: 7 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.