From c95a7c21597ec51f72b021e0a74be118cec72bc3 Mon Sep 17 00:00:00 2001
From: mrmr1993
Date: Sat, 20 Feb 2016 17:47:36 +0000
Subject: Use for (not for own) when iterating over an event's properties

Moving to for own broke find mode history (and thus also next/previous).
This reverts that part of commit
56fed2ac6663d99ca03023f3ffa313c51de5fe32.
---
 pages/hud.coffee | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/pages/hud.coffee b/pages/hud.coffee
index 872a9c28..33700122 100644
--- a/pages/hud.coffee
+++ b/pages/hud.coffee
@@ -16,7 +16,8 @@ document.addEventListener "keydown", (event) ->
   inputElement = document.getElementById "hud-find-input"
   return unless inputElement? # Don't do anything if we're not in find mode.
   transferrableEvent = {}
-  for own key, value of event
+  # NOTE(mrmr1993): We use for, not for own, here, since we want to access members from the Event prototype.
+  for key, value of event
     transferrableEvent[key] = value if typeof value in ["number", "string"]
 
   if (event.keyCode in [keyCodes.backspace, keyCodes.deleteKey] and inputElement.textContent.length == 0) or
-- 
cgit v1.2.3