Open marcevrard opened 6 years ago
My best guess without images is that the 'stuck' highlight is the browser's rendering of actually-selected text in non-focused cells. I'm uncertain off the top of my head how to avoid this with just css, as I can't seem to get anything to override the built-in webkit ::selection
style :confused:
Scratch that, my mistake. My guess is still that the 'highlights' which remain 'stuck' are actually the selected text in that cell's CodeMirror instance. But, CodeMirror applies the selection styling, so it can be overriden.
I've added a screencast and updated the title (and the first comment) since only scrolling seems sufficient to trigger the phenomenon.
Hmm, ok, that is something else, then. Will investigate...
Seems like overlays were not getting removed correctly. Should be fixed by #31
Nice, indeed, it's working on my side with version 0.2.0.
Though I have another issue now, not sure it's related. If I highlight a word, it will not be highlighted in the inactive cells not visible at the moment of the selection. This happens whether the following option is selected or not:
Only apply highlights to editors which are visible in the scrolled view. This may offer performance benefits for larger notebooks
The highlighting appears to be stuck on the selected word after scrolling down when
only_cells_in_scroll
istrue
.Versions:
The
notebook.json
: