This way, only one char's left and right edges are used, instead of its
(logical) neighbour's right edges.

In bidi content, this avoids trying to scroll to two logically close,
but visually far apart positions in some situations.

This reverts commit e7b737c8.

into a form that CodeMirror can understand.

Since moving the highlighting frontier forward when doing
things like getTokenAt is not safe at all.

Also properly update highlighting frontier when a change
happens.

Since the vim bindins are depending on that

FEATURE: Mouse button clicks can now be bound in keymaps by using
names like `"LeftClick"` or `"Ctrl-Alt-MiddleTripleClick"`. When bound
to a function, that function will be passed the position of the click
as second argument.

FEATURE: The behavior of mouse selection and dragging can now be
customized with the
[`configureMouse`](http://codemirror.net/doc/manual.html#option_configureMouse)
option.

To avoid false negatives due to window scrolling

Which often caused strangeness around empty lines

Issue #4307

Since rollup is now adding those

The identifier-quote that a language uses around identifiers can now
be defined using "identifierQuote" when defining a mimetype.
Previously, backticks where hardcoded, but this is not standard SQL
(which uses double quotes). For example, SQLite defines double quotes
as preferred way to quote identifiers:
http://sqlite.org/lang_keywords.html

Issue #4618

https://vi.stackexchange.com/questions/6061

1. End of wrapped line in bidi content is wrong (my mistake)
2. coordsChar({left:0, top: *}) in bidi content is wrong after Marijn's code
   style changes

ES5, breaking up of whitespace tokens

* Enable most in phantom
* Enable all in !phantom
* Disable two that trigger L1 which we don't do correctly currently
* Revert commit 5cc5d7f50efc7a016485f017a603c4fa2b035266 (L1 tests)