From 9501b9f3d3355aeef8964efbdb050221724ffbcf Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Lorenz=20H=C3=BCbschle-Schneider?=
 <lorenz-dev@lgh-alumni.de>
Date: Sun, 10 Aug 2014 18:59:15 +0100
Subject: [PATCH] Fix history keybindings for keypress

because ASCII != keydown code in JS m(
---
 js/glowingbear.js | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/js/glowingbear.js b/js/glowingbear.js
index d7e6500..98a96ae 100644
--- a/js/glowingbear.js
+++ b/js/glowingbear.js
@@ -1604,7 +1604,7 @@ weechat.directive('inputBar', function() {
                 }
 
                 // Arrow up -> go up in history
-                if (code === 38) {
+                if ($event.type === "keydown" && code === 38) {
                     $scope.command = models.getActiveBuffer().getHistoryUp($scope.command);
                     // Set cursor to last position. Need 0ms timeout because browser sets cursor
                     // position to the beginning after this key handler returns.
@@ -1617,7 +1617,7 @@ weechat.directive('inputBar', function() {
                 }
 
                 // Arrow down -> go down in history
-                if (code === 40) {
+                if ($event.type === "keydown" && code === 40) {
                     $scope.command = models.getActiveBuffer().getHistoryDown($scope.command);
                     // We don't need to set the cursor to the rightmost position here, the browser does that for us
                     return true;