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)
Firefox Graveyard
Panorama
Tracking
(Not tracked)
RESOLVED
FIXED
Firefox 4.0b5
People
(Reporter: iangilman, Assigned: raymondlee)
References
Details
Attachments
(2 files, 3 obsolete files)
2.59 KB,
patch
|
Details | Diff | Splinter Review | |
1021 bytes,
patch
|
Details | Diff | Splinter Review |
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).
Updated•15 years ago
|
Whiteboard: b4
Updated•15 years ago
|
Priority: -- → P2
Assignee | ||
Comment 1•15 years ago
|
||
Updated the magic numbers to constants.
Attachment #465577 -
Flags: review?(dolske)
Attachment #465577 -
Flags: feedback?(dolske)
Comment 2•15 years ago
|
||
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: -- → ---
Updated•15 years ago
|
Attachment #465577 -
Flags: review?(dolske)
Attachment #465577 -
Flags: review+
Attachment #465577 -
Flags: feedback?(dolske)
Attachment #465577 -
Flags: approval2.0+
Assignee | ||
Updated•15 years ago
|
Assignee: nobody → raymond
Status: NEW → ASSIGNED
Updated•15 years ago
|
Keywords: checkin-needed
Comment 3•15 years ago
|
||
There's a few number key codes in browser-tabview.js too
Assignee | ||
Updated•15 years ago
|
Summary: Use proper constants in setTabViewFrameKeyHandlers → Use proper KeyEvent constants for Tab Candy code
Assignee | ||
Comment 4•15 years ago
|
||
* 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)
Assignee | ||
Updated•15 years ago
|
Attachment #465577 -
Attachment description: v1 → v1 for _setTabViewFrameKeyHandlers
Assignee | ||
Updated•15 years ago
|
Attachment #466532 -
Attachment is patch: true
Attachment #466532 -
Attachment mime type: application/octet-stream → text/plain
Updated•15 years ago
|
QA Contact: tabcandy → tabcandy
Reporter | ||
Comment 5•15 years ago
|
||
Comment on attachment 466532 [details] [diff] [review]
v1 for _setBrowserKeyHandlers
Looks good to me.
Attachment #466532 -
Flags: feedback?(ian) → feedback+
Comment 6•15 years ago
|
||
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+
Assignee | ||
Comment 7•15 years ago
|
||
r+ Dolske f+ Ian
Attachment #466532 -
Attachment is obsolete: true
Assignee | ||
Updated•15 years ago
|
Attachment #466874 -
Flags: approval2.0?
Updated•15 years ago
|
Attachment #466874 -
Flags: approval2.0? → approval2.0+
Assignee | ||
Comment 8•15 years ago
|
||
Attachment #465577 -
Attachment is obsolete: true
Assignee | ||
Comment 9•15 years ago
|
||
Attachment #466874 -
Attachment is obsolete: true
Updated•15 years ago
|
Attachment #468894 -
Attachment is patch: true
Attachment #468894 -
Attachment mime type: application/octet-stream → text/plain
Comment 10•15 years ago
|
||
http://hg.mozilla.org/mozilla-central/rev/bd255a24160a
http://hg.mozilla.org/mozilla-central/rev/17d24407f975
Status: ASSIGNED → RESOLVED
Closed: 15 years ago
Keywords: checkin-needed
Resolution: --- → FIXED
Whiteboard: b4
Target Milestone: --- → Firefox 4.0b5
Updated•9 years ago
|
Product: Firefox → Firefox Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•