Closed Bug 595518 Opened 14 years ago Closed 14 years ago

After focusing the icon in the right-top corner in tabcandy, trying to activate tabcandy afterwards goes imediately back to normal view

Categories

(Firefox Graveyard :: Panorama, defect)

x86
Linux
defect
Not set
normal

Tracking

(blocking2.0 betaN+)

VERIFIED FIXED
Firefox 4.0b7
Tracking Status
blocking2.0 --- betaN+

People

(Reporter: smaug, Assigned: raymondlee)

References

Details

Attachments

(1 file, 3 obsolete files)

I don't know what the icon is for, but seems like it somehow exists the tabcandy view. But the focus also stays in that icon, so that if I afterwards try to go to TabCandy, TabCandy is activated by it exits immediately. Sounds like the icon was tested only on OSX, where focus handling is quite different (and IMO OSX in general has pretty insane focus handling).
blocking2.0: --- → ?
Blocks: 594094
Attached patch V1 (obsolete) — Splinter Review
This will require the patch for bug 595191 to land first because this patch uses the blurAll method
Assignee: nobody → raymond
Depends on: 595191
Pushed to try and waiting for the results
Passed try
Comment on attachment 475031 [details] [diff] [review] V1 + if (navigator.platform.indexOf("Mac") != -1) { + charCode = 160; + eventObject = { altKey: true }; + } else { + charCode = 32; + eventObject = { ctrlKey: true }; + } Use KeyEvent.DOM_VK_SPACE instead of the 32, and comment the 160 to make it clear that that's the character code for option + space. Have you verified this fix on Windows? I'm a little confused by this... isn't it just space we're looking for? Or is option space a different character code? Also, shouldn't we be using
(In reply to comment #4) > I'm a little confused by this... isn't it just space we're looking for? Or is > option space a different character code? Also, shouldn't we be using Please ignore these lines; earlier draft... clearly I figured it out. :)
Attached patch v2 (obsolete) — Splinter Review
I've tested this patch on Windows 7 and it worked fine.
Attachment #475031 - Attachment is obsolete: true
Attachment #475120 - Flags: review?(dietrich)
Comment on attachment 475120 [details] [diff] [review] v2 It requires the patch for bug 595191 to land first because it depends on the blurAll method
Comment on attachment 475120 [details] [diff] [review] v2 r=me. before landing, please add some commentary to the test.
Attachment #475120 - Flags: review?(dietrich) → review+
Updated patch with comments, as well as r+ in commit message. Also, the test had the wrong bug number (595191); fixed.
Attachment #475120 - Attachment is obsolete: true
Attachment #475225 - Flags: approval2.0?
Also note that this patch still requires bug 595191 to land first.
You can clear the approval request - marked blocking betaN+
blocking2.0: ? → betaN+
Attachment #475225 - Attachment description: patch v3 (ready for check in, except needs a+ mention in commit message) → patch v3 (ready for check in, needs to land after 595191)
Attachment #475225 - Flags: approval2.0?
Blocks: 595763
Updated patch with comment message, and remerged with 595191.
Attachment #475225 - Attachment is obsolete: true
Keywords: checkin-needed
Status: NEW → RESOLVED
Closed: 14 years ago
Keywords: checkin-needed
Resolution: --- → FIXED
Target Milestone: --- → Firefox 4.0b7
verified on recent nightly builds of minefield
Status: RESOLVED → VERIFIED
Product: Firefox → Firefox Graveyard
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: