Closed Bug 555607 Opened 14 years ago Closed 1 month ago

[10.4] Shortcut command + arrows does not go back or forward in History

Categories

(Camino Graveyard :: Accessibility, defect)

PowerPC
macOS
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED INCOMPLETE

People

(Reporter: r.mozley, Unassigned)

Details

(Keywords: regression)

User-Agent:       Mozilla/5.0 (Macintosh; U; PPC Mac OS X 10.4; en-GB; rv:1.9.0.18) Gecko/2010022311 Camino/2.0.2 (like Firefox/3.0.18)
Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X 10.4; en-GB; rv:1.9.0.18) Gecko/2010022311 Camino/2.0.2 (like Firefox/3.0.18)

The shortcut command + left & right arrows does not cycle through the browser History when using Mac OS X Tiger 10.4 and Camino 2.0.x

Reproducible: Always

Steps to Reproduce:
1. Open browser.
2. Visit some web pages in a single window or tab.
3. Enter shortcut Command+Left-Arrow or click back button, then enter shortcut Command+Right-Arrow.
Actual Results:  
Nothing.

Expected Results:  
To move back and forward in browser history.

This appears not to happen in Leopard or Snow Leopard (10.5 and 10.6 respectively).
I'm going to confirm this based on Richard's verification of another report of this on the forum (and because trying to find a dev with 10.4 anymore is like looking for a needle in a haystack).

Since it apparently wasn't bug 530663 that broke this (as all 2.0.x releases are broken according to the forum post), my next guess was that this had been broken ever since bug 405744, but Eiichi commented in there on commit, and after an additional fix from Stuart, this was working fine in March 2008.  That's still a two-year window post-bug 405744, though :(
Status: UNCONFIRMED → NEW
Ever confirmed: true
Flags: camino2.0.3?
I tested this with official 2.0.2 on 10.4.
Shortcut command + arrows works going back or forwarding in History.
Eiichi, you are on Intel, iirc ?

Both Richard (who filed the bug) and the forum poster are testing on PPC.
http://forums.mozillazine.org/viewtopic.php?f=12&t=1820635
(In reply to comment #3)
> Eiichi, you are on Intel, iirc ?

Yes, on intel.
And  Camino 2.0.3pre latest nightly build (2010-03-28-12-2.0-M1.9) also works fine on 10.4 (Intel).
Richard, when you tested 10.5 in comment 0, was that on PPC or Intel?

Now that we've determined that on 10.4 this is actually PPC-only, we should make sure it doesn't also manifest on PPC on 10.5.
WFM with Camino 2.0.2 on 10.4 PPC.
Oh, umm... Sorry, I haven't actually tested this on 10.5 (I don't have Leopard at the moment). I was guessing that it doesn't happen from what philippe said in the forum.
(In reply to comment #7)
> Oh, umm... Sorry, I haven't actually tested this on 10.5 (I don't have Leopard
> at the moment). I was guessing that it doesn't happen from what philippe said
> in the forum.

OK, that's fine; I just wanted to make sure we knew what exactly had been tested :) cl can probably try 10.5 PPC late in the week.

Since hendy doesn't see this on his iBook, we're at a standstill here until we can figure out either 1) when this broke for Richard and the other guy in the forum and/or 2) what's different about the setup(s) of Richard/the other guy in the forums compared to hendy's iBook (which doesn't see the problem).
I've tested all the betas and they still exhibit the problem, for me anyway. Time I checked things back earlier.

Oh, and how do we check for differences compared to what Hendy has (not an easy task I would imagine)?
Ok, I've narrowed it down to between 2008-02-29 and 2008-03-31 builds. Shortcut works in the Feb. 29 build.
Bug 425519 is in the regression range, too, and it has broken strange things before (e.g. bug 527248 and something else that hendy fixed last year).  

I'd feel more comfortable if we had a 24 hour window (though I agree that bug 405744 is the most likely suspect).

http://bonsai.mozilla.org/cvsquery.cgi?treeid=default&module=Camino&branch=HEAD&branchtype=match&dir=mozilla%2Fcamino&file=&filetype=match&who=&whotype=match&sortby=Date&hours=2&date=explicit&mindate=2008-02-29&maxdate=2008-04-01&cvsroot=%2Fcvsroot
(In reply to comment #12)
> I'd feel more comfortable if we had a 24 hour window.

Don't worry, I'm still looking into it. ;)
OK, just to update you all, I've narrowed it down to two nightly builds. 2008-03-12 shortcut works and 2008-03-13 doesn't.
Bug 417466 is in that window and messes about with performKeyEquivalent, so that's my bet for the culprit now.
(In reply to comment #15)
> Bug 417466 is in that window and messes about with performKeyEquivalent, so
> that's my bet for the culprit now.

That landed on the 13th at 18:00 MozT, so that's not in the 2008-03-13 nightly (generated at 01:00 MozT):

http://bonsai.mozilla.org/cvsquery.cgi?treeid=default&module=Camino&branch=HEAD&branchtype=match&dir=&file=&filetype=match&who=&whotype=match&sortby=Date&hours=2&date=explicit&mindate=2008-03-12+00%3A00&maxdate=2008-03-13+01%3A00&cvsroot=%2Fcvsroot

Bug 420699?  (Bug 297080 also touches widget, but it's mouse events, so less likely.)

In any event, if this is something in widget/, we're not going to be able to block 2.0.3 on it unless there's some sort of stellar work-around possible in camino/.
Flags: camino2.0.3? → camino2.0.3-
Hendy, are you perhaps using an external keyboard with your iBook? Just a thought it may be connected to keyboards.
There's probably *something* we can log here (not sure what, though) and have Richard build with logging and find out more.

Also, Richard, does this problem persist in the experimental 1.9.2 builds?
(In reply to comment #18)
> Also, Richard, does this problem persist in the experimental 1.9.2 builds?

Oh, not tried those builds as of yet. I'll try them out on my test account as soon as I have time.
I've tested the latest experimental 1.9.2 build and this problem still occurs with that one.

Not sure if this is related or another bug but drop down sheet buttons require clicking twice (when using tap clicking with my track pad. Doesn't occur with mouse, strangely) only in Camino 2.0+
Oh, just thought, I should check if this other problem happens at the same point as this bug.
(In reply to comment #20)
> I've tested the latest experimental 1.9.2 build and this problem still occurs
> with that one.

OK.  I thought it probably would be there, but some of the Gecko keyhandling stuff has changed, so there was a chance it could have been fixed.

> Not sure if this is related or another bug but drop down sheet buttons require
> clicking twice (when using tap clicking with my track pad. Doesn't occur with
> mouse, strangely) only in Camino 2.0+
> Oh, just thought, I should check if this other problem happens at the same
> point as this bug.

Like bug 472634 (except it happens always)?
(In reply to comment #21)
> Like bug 472634 (except it happens always)?

Well yes, it happens quite often enough to get rather annoying. But in further testing I found that it was something in my prefs.js file that was causing this clicking problem. A new prefs file and adding in some of the extra options I've set seems to have cleared the problem.
Not sure which of the leftover user options could have caused it. I guess it's add one at a time testing.
We should try to track this for 2.1, though.
Flags: camino2.1?
For this bug I can no longer test things, iBook has gone back to work for use elsewhere. Last time I checked a nightly build it still seemed to be there (I forget which one in particular that I tested, might have been two or three months ago).

Seeing as this appears to be only affecting a very small number of users, it may be best to just drop the bug and point anyone with the problem to "fix" it with keyboard shortcuts in System Preferences.
(In reply to R P Mozley from comment #24)
> Seeing as this appears to be only affecting a very small number of users, it
> may be best to just drop the bug and point anyone with the problem to "fix"
> it with keyboard shortcuts in System Preferences.

I think that's what's ultimately going to happen; playground won't support 10.4, anyway.
Flags: camino2.1? → camino2.1-
Status: NEW → RESOLVED
Closed: 1 month ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.