Closed
Bug 363934
Opened 18 years ago
Closed 18 years ago
keyboard tab bar navigation broken
Categories
(Firefox :: Tabbed Browser, defect)
Tracking
()
RESOLVED
FIXED
People
(Reporter: Peter6, Unassigned)
References
Details
(Keywords: regression)
Attachments
(3 files, 1 obsolete file)
1.19 KB,
patch
|
Details | Diff | Splinter Review | |
2.67 KB,
patch
|
Gavin
:
review+
neil
:
superreview+
|
Details | Diff | Splinter Review |
3.18 KB,
patch
|
Details | Diff | Splinter Review |
Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.9a1) Gecko/20061214 Minefield/3.0a1 ID:2006121406 [cairo] repro: open multiple tabs focus 1 tab use leftarrow|rightarrow|home|end keys to navigate result: it works only the first time , nothing happens when you hit any of the above tabs after that http://bonsai.mozilla.org/cvsquery.cgi?module=PhoenixTinderbox&date=explicit&mindate=1165984140&maxdate=1166020919 ->Bug 330705
Comment 1•18 years ago
|
||
Isn't this fixed now that I partially backed out the patch from bug 330705?
Reporter | ||
Comment 2•18 years ago
|
||
Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.9a1) Gecko/20061214 Minefield/3.0a1 ID:2006121422 [cairo] No
Reporter | ||
Comment 3•18 years ago
|
||
it works only the first time , nothing happens when you hit any of the above <del>tabs</del> keys after that
Comment 4•18 years ago
|
||
This fixes it, but I'm not really sure why. Apparently, the adding of a functional blur method for xul elements, which I did in bug 330705, has caused this bug.
Reporter | ||
Comment 5•18 years ago
|
||
additional: if you quickly rightarrow, you can get to other tabs. So the focus is properly applied, but lost due to one or another timeout.
Updated•18 years ago
|
Summary: keyboard tab bar naviagtion broken → keyboard tab bar navigation broken
Comment 6•18 years ago
|
||
(In reply to comment #4) > This fixes it, but I'm not really sure why. > Apparently, the adding of a functional blur method for xul elements, which I > did in bug 330705, has caused this bug. Perhaps due to http://bonsai.mozilla.org/cvsblame.cgi?file=mozilla/toolkit/content/widgets/tabbrowser.xml&rev=1.216#669 ? </random guess>
Comment 7•18 years ago
|
||
Or perhaps the delayed setFocus stuff further down in updateCurrentBrowser.
Comment 8•18 years ago
|
||
(In reply to comment #6) > Perhaps due to Yes, thanks! That is the cause of the bug. When the tab is the focusedElement, it gets blurred now. The extra check I added prevents that. I copied it more or less from below, where a similar check is used. This should be very safe, but I wonder why this blur() line is even there. Maybe because of Mac problems showing the outline through the background tab or something?
Attachment #248784 -
Flags: review?(gavin.sharp)
Comment 9•18 years ago
|
||
(In reply to comment #8) > This should be very safe, but I wonder why this blur() line is even there. > Maybe because of Mac problems showing the outline through the background tab or > something? It seems to have been added by attachment 152579 [details] [diff] [review] from bug 175893, by Aaron. Maybe he remembers what it's for?
Comment 10•18 years ago
|
||
Also affects SeaMonkey tabbrowser btw.
Comment 11•18 years ago
|
||
Filed Bug 364969 for xpfe/.
Comment 12•18 years ago
|
||
Comment on attachment 248784 [details] [diff] [review] real patch Oops, sorry, the patch should use document.commandDispatcher.focusedElement instead of this.mCurrentBrowser.focusedElement.
Attachment #248784 -
Attachment is obsolete: true
Attachment #248784 -
Flags: review?(gavin.sharp)
Comment 13•18 years ago
|
||
Ok, this patch is for xpfe and toolkit. I haven't tested the xpfe version (my seamonkey build not working right now). I had an irc chat with Aaron on this. Basically he agreed that we should try to remove this code, but he suggested to me that I should file a new bug on that, and put the accompanying patch for the removal in there.
Attachment #251687 -
Flags: superreview?(neil)
Attachment #251687 -
Flags: review?(gavin.sharp)
Comment 14•18 years ago
|
||
Comment on attachment 251687 [details] [diff] [review] patch It's not obvious so I won't ask you to alter the patch but mCurrentTab hasn't been changed yet so that we don't technically need to check parent nodes here.
Attachment #251687 -
Flags: superreview?(neil) → superreview+
Comment 15•18 years ago
|
||
Comment on attachment 251687 [details] [diff] [review] patch Maybe add a comment explaining the check? ("Only blur the focused element if it isn't another tab, to avoid breaking keyboard tab navigation"?)
Attachment #251687 -
Flags: review?(gavin.sharp) → review+
Comment 16•18 years ago
|
||
Er, s/another/a/, I guess.
Comment 17•18 years ago
|
||
Comment 18•18 years ago
|
||
Checking in toolkit/content/widgets/tabbrowser.xml; /cvsroot/mozilla/toolkit/content/widgets/tabbrowser.xml,v <-- tabbrowser.xml new revision: 1.217; previous revision: 1.216 done Checking in xpfe/global/resources/content/bindings/tabbrowser.xml; /cvsroot/mozilla/xpfe/global/resources/content/bindings/tabbrowser.xml,v <-- t abbrowser.xml new revision: 1.174; previous revision: 1.173 done Checked in on trunk. I filed bug 367806 on actually removing this code again.
Status: NEW → RESOLVED
Closed: 18 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•