simple-drag-drop-text
simple-drag-drop-text copied to clipboard
Text Does Not Unhighlight
This may not at all be caused by simple-drag-drop-text, but the issue seemed to arrive after I updated the module.
After the module is activated for a selection, that selection highlight may never go away (i.e. the text remains highlighted). This does not affect further selection actions; it is just a visual issue. Unfortunately it means that new selections within the stuck-highlighted text are invisible (because the larger block is already highlighted).
I'm not altogether sure exactly what triggers the problem, and it doesn't happen every single time, but it seems to occur frequently since updating the module.
Here's a screenshot after the problem has occurred several times in the same document. Note that the caret is actually positioned at line 177, and there is no active selection.

The only way to get the extra highlighting to disappear seems to be closing the document window.
Same here...
Same to me, I found this temporary solution:
in the developer console, run the script
for(let el of document.querySelectorAll(".highlight.selection")){ el.remove() }
Same for me too (occasionally) Have not tried the command above.
Same here, even if I don't complete a drag & drop. I have disabled the package for now
Same here, even if I don't complete a drag & drop. I have disabled the package for now
Ditto
Same here...
@webdevian @nicolashainaux @l0gical @andreazorzi @roelofcoster Please do not comment "same here", use thumbs up on the original post instead. Such comments cause unnecessary notifications to people involved and do not contribute to solving the issue. Thank you for understanding
I'm commenting "same here" because I want this fixed and people to be notified.
FIX IT
I'm commenting "same here" because I want this fixed and people to be notified.
FIX IT
Please be aware, that the developer is providing this package for free and developing it in his free time.
:wave: Thank you for reporting this.
With Github sunsetting Atom by the end of the year, I am choosing to also sunset this plugin.
The behavior provided by this plugin comes out-of-the-box within Visual Studio Code, the editor recommended by Github/Microsoft as an alternative to Atom.
If someone else wants to fix this issue with a PR, I welcome the contribution.