Bug: Linux middle-click paste doesn't work and does different stuff depending on browser

[colinkeenan]

Issue Summary

Most applications in linux recognize the 2nd copy and paste buffer which contains whatever was last highlighted and can be pasted by clicking the middle (scroll-wheel) button of the mouse. Ghost doesn't seem to recognize middle-click paste, and behaves completely differently depending on the browser. In Firefox 32.0, it doesn't do anything unless a URL had been highlighted, then it actually goes to that url. In Chrome 39.0.2145.4 dev (64-bit), it sometimes works, but almost always inserts a '$' instead.

Steps to Reproduce

1. Run Ghost on a Linux machine
2. Try it in both Firefox 32.0 and Chrome 39.0.2145.4 dev (64-bit)
3. Start a New Post and try highlight & middle-click paste. Especially, try it on a URL. In Chrome, try it repeatedly until it works.

This is a bug because middle-click paste is a very common way of doing a copy and paste in Linux, especially among coders. Those used to middle-click paste will find it very frustrating to constantly have to re-copy and paste stuff when the first method done by habit didn't work.

Technical details

• Ghost Version: master - latest commit: stable - a21ce4d
• Client OS & Server OS at http://localhost:2368/ghost/editor/: x86_64 GNU/Linux, Arch Linux 3.16.2-1-ARCH
• Node Version: v0.10.31
• Browser: Firefox 32.0 and Google Chrome Version 39.0.2145.4 dev (64-bit)
• Database: ghost-dev.db (default sqlite)

[ErisDS]

Hi @colinkeenan, thanks for the incredibly detailed bug report!

I can see that this would be incredibly frustrating for comfortable linux users. Unfortunately, I think they are two, unrelated, but known bugs in CodeMirror. The Firefox one seems to be stuck, but the chrome one looks like it might be fixed in a later version of CodeMirror than we are currently using.

Therefore a version bump of CodeMirror should at least solve one of these.

[ErisDS]

After further investigation, it doesn't look like the latest version of codemirror does contain a fix for either issue. Therefore I'm going to close this as wontfix against issue #1294 - this is an issue where we track all of these sorts of problems with the editor so that when we come to do the overhaul, we can take these into account.