You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When using vim as the text editor keymap, syntax highlighting obscures the cursor. There don't appear to be any relevant codemirror extensions settings.
This occurs in Firefox and Chrome on OSX 10.15.4. Although on Chrome the edge of the cursor is just barely visible, so Chrome+zoom page is my current workaround.
Expected behavior
I think the cursor should be visible on top of the highlighting.
The text was updated successfully, but these errors were encountered:
This is difficult and not specific to this extension. Long story short, the cursor is usually placed on top with z-index 1, but in the vim mode it is placed under the text with z-index 3. Now, all the token-based highlighters, including the built-in search of JupyterLab and the match highlighter add-on from codemirror create the highlight effect by adding a background to the token; we cannot have a cursor between the background and the text in HTML (as far as I know).
The line highlight feaure works this problem around by using a custom presentation layer which is below all tokens (and below the cusors); it might be possible to rewrite our highlights to use a similar mechanism (the positioning is possible - this is how cursros are made), but not trivial.
One way around it would be to change z-index of the cursor to place in at the top and make it semi-transparent (or only border/outline, with transparent inside).
Description
When using vim as the text editor keymap, syntax highlighting obscures the cursor. There don't appear to be any relevant codemirror extensions settings.
Firefox:
This occurs in Firefox and Chrome on OSX
10.15.4
. Although on Chrome the edge of the cursor is just barely visible, so Chrome+zoom page is my current workaround.Expected behavior
I think the cursor should be visible on top of the highlighting.
The text was updated successfully, but these errors were encountered: