Firefox - It selects whole node instread of text

Often when I try to click into the text of a node the whole node gets selected instead of placing the cursor in the desired place. When I click on other nodes they get selected to.

Steps to reproduce

I did not figure out how to reproduce this bug, but it happens very regularly for me.

Expected result

Cursor gets placed at the right place in the text of the node.

Actual result

Whole node gets selected


Which operating system are you using?
Ubuntu 19.10

Which browser are you using?
Firefox 70.0.1 (64bit)

Are you using any third-party scripts for Dynalist, e.g. PowerPack?

Have you tried without Powerpack 3? Was there any errors in the javascript console?

1 Like

Thanks for the suggestion! It seems to be the PowerPack. I guess I will use it only in the Desktop App from now on.

Thanks for confirming. I will need to do something about it sooner or later since quite some people are having trouble with it already and it’s breaking a lot of functionality.

1 Like

Thank you! It is partilly my fault because I think the PowerPack is not intended to work properly in Firefox. @Piotr mentioned that. I just copied the script into Tampermonkey for Firefox.

I experienced the same behavior without PowerPack too :confused:

It is really hard to reproduce, in the gif it looks like I intentionally try to trigger it but I have no idea what I am doing.

Sorry to bother you, but this problem still excists. I was too fast resolving it :confused:

Were you able to take a look at the javascript console to see if any errors popped up?

1 Like

I think I found the source. It was an addon I had installed. Problem solved :slightly_smiling_face:

Got it, thanks for following up again.

@Shida Okay, a quick follow up. The problem still exists, I just did not notice it because I don’t use Dynalist much in the browser. But when it occurs it really bothers me and makes the app near to unusable with the mouse.


I’m guessing 3rd party issues again? Not seeing this on my end and not hearing anyone else run into this. Could you check developer console for any errors, and see if it’s caused by any browser extensions?