Deuntje Posted November 26, 2021 Report Posted November 26, 2021 I didn’t see any bugtracker on your site, so hereby a bugreport in the forum as well. When using enpass browser extension in Firefox or Chrome with sites which include iframes and forms the extension gives the following error in browsers console: Error: Promised response from onMessage listener went out of scope 80 background.js:8:59712 The extension then steals focus to the first field of the form, after that it’s impossible to select text on the iframed-webpage, the extension returns the focus directly to the form again. I created a page where I can reproduce this behavior: https://www.db-works.nl/enpass-bugreport/ , please check this site with steps to reproduce. Tested with: Windows 10 Enterprise Version 20H2 (OS build 19042.1165) Firefox 94.0.2 (64-bits) + Enpass extension for firefox version 6.7.0 Chrome Version 96.0.4664.45 (Official Build) (64-bit) + Enpass extension for chrome version 6.7.4 Hopefully you can fix this bug. 5
drob Posted December 13, 2021 Report Posted December 13, 2021 I think I'm having the same issue after updating the extension in chrome. I have noticed it on several websites where the first field of a form is always in focus no matter which field I click on. I found I can tab to get to other fields or it is easier to disable the enpass extension. This is driving me nuts in Salesforce! 1
stealth Posted December 15, 2021 Report Posted December 15, 2021 I can confirm that I faced the same issue. Moreover when Enpass extension is active I can't select the values from the dropdowns: the list is immediately closed because it loses the focus. 1
Abhishek Dewan Posted December 17, 2021 Report Posted December 17, 2021 Hi @Deuntje, @drob, @stealth You will be glad to know that our dedicated tech team has reproduced the bug on their end due to which this issue is occurring, and they are now working on a possible fix (to be implemented in the upcoming Enpass versions). In the meantime, please add the web pages on which this issue is occurring to the block list of your Enpass Extension Settings page. Here is how you can do it - On your browser, go to its Settings → Extensions → Enpass Extension → Details. A new page will open. Please scroll down on that page and select “Extension Options“. On the Enpass Extension Settings page, scroll down to “ Inline Autofill Menu Blocklist“, copy the URL of the webpage where this issue is occurring and paste it in the “ Add URL “ field followed by an asterisk in the end. #SI-2505 Appreciate your patience and co-operation in the meantime. 3
Deuntje Posted March 3, 2022 Author Report Posted March 3, 2022 On 12/17/2021 at 10:12 AM, Abhishek Dewan said: You will be glad to know that our dedicated tech team has reproduced the bug on their end due to which this issue is occurring, and they are now working on a possible fix (to be implemented in the upcoming Enpass versions). Any updates on this case? When can we expect the fix?
Abhishek Dewan Posted March 4, 2022 Report Posted March 4, 2022 Hi @Deuntje Our dedicated team is still working to resolve this issue. I am unfortunately unable to provide you with any timeline, but please know that I am closely following this case and will inform you if there are any updates here on this forum. Enpass appreciates your patience in the meantime.
Sunil Surendran Posted March 22, 2022 Report Posted March 22, 2022 Since the introduction of the "Autofill Popup Menu" in Enpass, it has been difficult to navigate the AWS console once signed in. In the AWS services where filters are available, the Filter block gets auto-selected once the page loads. Even if we click elsewhere on the page, the Filter context menu of the particular AWS service pops up and makes its harder to click elsewhere. For eg: in the EC2 console page even if we select the instance row, the Filter menu pops up back instantly. Observed this in various other sections of Ec2 launch page as well (While going through the menu of launching an instance). The Fix was to disable the "Show Inline Autofill Popup Menu" in Browser extension settings of Enpass. Can you please look into this issue.
zoeck Posted March 25, 2022 Report Posted March 25, 2022 (edited) On 12/17/2021 at 10:12 AM, Abhishek Dewan said: In the meantime, please add the web pages on which this issue is occurring to the block list of your Enpass Extension Settings page. This Workaround is not working for me! It took me a long time to realize that the problem comes from the Enpass plugin. I can only bypass the problem by deactivating the "Show Inline Autofill Menu" option in the plugin. (or if you deactivate the plugin completely) /UPDATE: The * Wildcard in the block list is only working for the "top level", i have to add it to "http://domain.com/*/*" after that it worked Edited March 25, 2022 by zoeck
HansMu158 Posted April 9, 2022 Report Posted April 9, 2022 (edited) I have the same problem and would really appreciate a fast solution other than deactivating the Auto Fill Menu. And I am also quite sure that many other users will have this problem but have not yet figured out that Enpass is causing this. Edited April 9, 2022 by HansMu158 added last sentence
MacFreek Posted May 13, 2022 Report Posted May 13, 2022 (edited) Thanks for tracking this down to iframes and Enpass extension. I can confirm that this issue is not limited to Firefox; I have the same problem with Opera (which is a Chromium-based browser). And because of this issue, I can't fill in forms on a Jira ticketing system, which is frequently used in our organisation. (And yes, it took me, and some of the support staff some time too to trace it to a bug in the Enpass extension! This was a painful dent in the reputation of Enpass to me! ) Thanks for informing us about the workarounds. I have deactivated the Auto Fill Menu; The feature is nice, but I rather stay on a more robust software track instead of dealing with features that are released prematurely. (And if I sound grumpy, that's because I've been dealing with this issue for the last months and only now realised that Enpass is the source of these problems) Edited May 13, 2022 by MacFreek
TheDetective Posted February 10, 2023 Report Posted February 10, 2023 Have there been any updates on a fix for this? I'm dealing with this exact issue as well.
Abhishek Dewan Posted February 13, 2023 Report Posted February 13, 2023 Hi @TheDetective To assist you better with this concern, please share the below details with me - The version of the Enpass app, OS, Enpass Extension and browser you are using. The URL of the webpages on which you are facing this concern. A screenshot of any error occurring or a short video showing this behavior would be helpful. Note - You can share the recording with us at support@enpass.io and mention this forum.
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now