~glacambre/firenvim

ref: 076c1a4f04db2173afb395d0af8c63a5bbcab6a8 firenvim/src d---------
36a47bdf — lolimay 11 months ago
improve: add callback as an optional argument to handle eval_js result
Make sure we're only evaluating expressions, not statements
Improve build system
Implement thunderbird support
Implement key ignore

Closes #717
Redraw.ts: remove guifontset handling

Closes #689
Add keycodes to key events generated by press_keys
FirenvimElement.ts: lower z-index for vimium

Closes #732
Remove persistent server
CSSUtils: change selector syntax

Using #XXX caused issues when XXX started with a number, because the CSS
spec disallows that.

https://www.w3.org/TR/CSS21/syndata.html#value-def-identifier
FirenvimElement: use MutationObserver to track element presence in page
Fix modifiers not being registered for special keys

This prevented <C-CR> from working.
content.ts: fix style issue
d788cf6a — Sean Mackesey 1 year, 3 months ago
Fix CodeMirrorEditor for JupyterLab support

Modified the regexp used to detect the CodeMirror root element during
CodeMirror detection. Now it checks to make sure the class it is looking for
*starts* with CodeMirror, as opposed to just containing “CodeMirror”.
This prevents it from matching `jp-CodeMirrorEditor`, which is a Jupyter
wrapper class that doesn’t expose the correct API.
Fix RPC mechanism being broken

The problem was that in trying to selectively answer to messages from
the neovim frame, the content script was made deaf to any request from
the backround script. This is fixed by ordering functions into
categories, e.g. global, active-content and "frame" and performing
checks tied to the categories before answering.
Make firenvim work consistently across frames

There was a race condition which sometimes prevented Firenvim from
working on inputs located in frames. This was caused by the wrong
content script answering the Firenvim frame's queries.
Make chrome tests more reliable on windows

Chrome tests are pretty unreliable on windows. I suspect this is because
windows is slow and has potentially racy code in the testsuite. This is
fixed by removing the race.
Use webpack to conditionally import browser polyfill
background.ts: make password longer

An excellent idea suggested by bovine3dom
Testsuite: expose reload function in test mode to make tests more robust
Next