From 6c861211206558e2e63f0f06b89ea7a61183a157 Mon Sep 17 00:00:00 2001
From: Dan Stillman <dstillman@zotero.org>
Date: Thu, 21 Mar 2019 04:51:32 -0400
Subject: [PATCH] Use onChange instead of onInput for Search component

React uses onChange for form elements (and complains if it's absent)
even when the underlying event is oninput.
---
 chrome/content/zotero/components/search.jsx | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/chrome/content/zotero/components/search.jsx b/chrome/content/zotero/components/search.jsx
index 7fed3ca4e4..872d301da3 100644
--- a/chrome/content/zotero/components/search.jsx
+++ b/chrome/content/zotero/components/search.jsx
@@ -23,7 +23,7 @@ class Search extends React.PureComponent {
 		};
 	}
 	
-	handleInput = (event) => {
+	handleChange = (event) => {
 		var value = event.target.value;
 		// Update controlled value and cancel button immediately
 		this.setState({
@@ -62,7 +62,7 @@ class Search extends React.PureComponent {
 			<div className="search">
 				<input
 					type="search"
-					onInput={this.handleInput}
+					onChange={this.handleChange}
 					onKeyDown={this.handleKeyDown}
 					ref={this.inputRef}
 					value={this.state.immediateValue}