Closed Bug 586719 Opened 15 years ago Closed 15 years ago

Use proper KeyEvent constants for Tab Candy code

Categories

(Firefox Graveyard :: Panorama, defect, P2)

defect

Tracking

(Not tracked)

RESOLVED FIXED
Firefox 4.0b5

People

(Reporter: iangilman, Assigned: raymondlee)

References

Details

Attachments

(2 files, 3 obsolete files)

From our dolske's review of bug 574217: > >+ _setTabViewFrameKeyHandlers: function() { > > Instead of the various magic numbers in this function, you really ought to be > using KeyEvent.DOM_VK_BLAH (.DOM_VK_TAB, .DOM_VK_RIGHT, etc).
Whiteboard: b4
Blocks: 586788
Priority: -- → P2
Updated the magic numbers to constants.
Attachment #465577 - Flags: review?(dolske)
Attachment #465577 - Flags: feedback?(dolske)
Mass moving all Tab Candy bugs from Mozilla Labs to Firefox::Tab Candy. Filter the bugmail spam with "tabcandymassmove".
Product: Mozilla Labs → Firefox
Target Milestone: -- → ---
Attachment #465577 - Flags: review?(dolske)
Attachment #465577 - Flags: review+
Attachment #465577 - Flags: feedback?(dolske)
Attachment #465577 - Flags: approval2.0+
Assignee: nobody → raymond
Status: NEW → ASSIGNED
There's a few number key codes in browser-tabview.js too
Summary: Use proper constants in setTabViewFrameKeyHandlers → Use proper KeyEvent constants for Tab Candy code
Attached patch v1 for _setBrowserKeyHandlers (obsolete) — Splinter Review
* Replaced a number with KeyCode.DOM_VK_*, that's the only number I can use in this part of code based on http://mxr.mozilla.org/mozilla-central/source/dom/interfaces/events/nsIDOMKeyEvent.idl * Fixed an issue which changing the active group in the reverse order was broken.
Attachment #466532 - Flags: review?(dolske)
Attachment #466532 - Flags: feedback?(ian)
Attachment #465577 - Attachment description: v1 → v1 for _setTabViewFrameKeyHandlers
Attachment #466532 - Attachment is patch: true
Attachment #466532 - Attachment mime type: application/octet-stream → text/plain
QA Contact: tabcandy → tabcandy
Comment on attachment 466532 [details] [diff] [review] v1 for _setBrowserKeyHandlers Looks good to me.
Attachment #466532 - Flags: feedback?(ian) → feedback+
Comment on attachment 466532 [details] [diff] [review] v1 for _setBrowserKeyHandlers > charCode == 160) { // alt + space ... > (charCode == 96 || charCode == 126)) { You could use |"x".charCodeAt(0)|, but I guess it's fine as-is too. >+++ b/browser/base/content/tabview/groupitems.js Tue Aug 17 11:01:00 2010 +0800 Please put these changes into a separate bug. Bugs are cheap, and one issue per bug makes Hg history easier to understand. r+ with that change.
Attachment #466532 - Flags: review?(dolske) → review+
Attached patch v2 for _setBrowserKeyHandlers (obsolete) — Splinter Review
r+ Dolske f+ Ian
Attachment #466532 - Attachment is obsolete: true
Attachment #466874 - Flags: approval2.0?
Attachment #466874 - Flags: approval2.0? → approval2.0+
Attachment #466874 - Attachment is obsolete: true
Attachment #468894 - Attachment is patch: true
Attachment #468894 - Attachment mime type: application/octet-stream → text/plain
Status: ASSIGNED → RESOLVED
Closed: 15 years ago
Keywords: checkin-needed
Resolution: --- → FIXED
Whiteboard: b4
Target Milestone: --- → Firefox 4.0b5
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: