Chrome Extension Watching Clicks

[Zigsaz]

Chrome Extension Watching Clicks

Hello,

I've been using Enpass for a few months now and have been very please (bought it almost immediately via the smartphone license).

However I have found one annoyance. I do web development full time and noticed that Chrome was constantly warning about click handler's taking some 300+ms. I ended up realizing it was the Enpass extension that was taking up a huge majority of this time (~70ms after disabling the extension).
What exactly is Enpass doing with such click events? I assume it's looking for fields to autofill? Is there any way to disable this and not invoke the extension at all until the hotkey is pressed?

Thanks

[Guest Akash Vyas]

Hey @Zigsaz

Wow, glad to know that you like Enpass and love doing web development. Keep 'em up!!

16 hours ago, Zigsaz said:

What exactly is Enpass doing with such click events? I assume it's looking for fields to autofill?

Enpass monitors the button click events for Login/Submit buttons to take the further actions.

16 hours ago, Zigsaz said:

Is there any way to disable this and not invoke the extension at all until the hotkey is pressed?

 

Sorry to say that there is no way to stop Enpass from monitoring the click events, and you have to disable the Enpass extension for that.

16 hours ago, Zigsaz said:

Chrome was constantly warning about click handler's taking some 300+ms. I ended up realizing it was the Enpass extension that was taking up a huge majority of this time (~70ms after disabling the extension).

I would really appreciate if you can throw more light on it i.e.  when and why Chrome is warning you while developing something. Understand that would open doors for us to understand the real cause behind the scene and if possible we will fix that.

Cheers!

[Zigsaz]

Hi @Akash Vyas,

Certainly, I can give as much info as I could dig up.

The warnings appear in Chrome's devconsole when you have logging set to include Verbose (previous versions of Chrome had this disabled by default I believe). Here's an example:

Obviously 200-300ms is no big deal for average users, but I was looking for reasons why our animations were feeling a bit choppy. And when I looked at a timeline trace of the click I noticed a good chunk of the time was spent in Enpass' content.js.

I took a cursory look through content.js, but couldn't make much of it since it had been minified. However I did notice in the DOM that Enpass was attaching data to some 300 elements on the page, so perhaps there might be some way to reduce what elements it considers important?

 

Thanks for looking into it!

Edited August 24, 2017 by Zigsaz

[Guest Akash Vyas]

Hey @Zigsaz

Thanks for sharing the detailed explanation. I've shared it with the dev team to look into it further and I'll keep you posted. 

Thanks for your cooperation.