* allow disabling of switch to settings behaviour
* whitelist penguin.linux.test for edit server (ChromeOS/Crostini)
* fix context menu on newer Chromes (#158)
* honour edit_server_host instead of hard-coding 127.0.0.1
* use the Chrome extension UI to set keyboard shortcuts.
* fix handling of spellcheck=false nodes for Gmail (#171, #162)

v1.15 (Same version as previous AMO version v1.14.2)


* Now builds for Firefox using WebExtension hooks
* Use chrome.notifications instead of webkitNotifications
* Use <div> with style instead of inline <img> for edit button
* fake "input" event to stop active page components overwriting text area</div>

dispatch "input" event to textarea after update

Some sites (looking at you, fastmail.fm) apparently maintain a shadow copy of a textarea's contents,
updating it from `change` events on the real textarea. Unfortunately, when `emacs_chrome` directly updates
the real textarea with text received from emacs, the shadow copy does not see these changes.
The user (me) is then surprised to see that upon submitting the web page (i.e. `Send`ing the email),
the edits made in emacs have disappeared, even though they were visible in the textarea.

This commit forces an `input` event to be dispatched to the textarea after its value has been set
with the new contents received from emacs, and fixes the problem (for fastmail.fm , at least)

Edit with Emacs is an extension for Firefox/Chrome(ium)
that allows you to edit text areas on your browser in a more full
featured editor. It does this in conjunction with an "Edit Server"
which services requests by the browser. This is because extensions
cannot spawn new processes as a security measure.

The extension packages native elisp version that can be run inside
GNU Emacs itself, just follow the instructions from the options page
of the extension. It has been known to work with GNU Emacs and
Aquamacs (MacOS); it is presently not compatible with XEmacs.

Other example edit servers can be found at the project homepage. There
is no reason why other server scripts could not spawn other editors
and currently a number of servers support the simple URL based
protocol.

This extension is licensed under the GPL v3 and development versions
can be found at: http://github.com/stsquad/emacs_chrome