This repository has been archived by the owner on Dec 11, 2019. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 975
Enabling Enpass causes browser to hang #6984
Labels
Comments
seems like either this never worked or the muon support changed in v54, I think we'll have to hide the option. |
We'll use this bug for adding that support but it isn't a priority vs other things. I'll add a new bug for tracking hiding the setting. |
Closed
andrewalker
added a commit
to andrewalker/browser-laptop
that referenced
this issue
Jun 18, 2017
This reverts commit 29a8223. According to issue brave#7778, particularly the comment by @mcg, support for Enpass is already working. So the option can be re-enabled. Fixes brave#7778, brave#5097, brave#6984.
andrewalker
added a commit
to andrewalker/browser-laptop
that referenced
this issue
Jun 18, 2017
This reverts commit 29a8223. According to issue brave#7778, particularly the comment by @mcg, support for Enpass is already working. So the option can be re-enabled. Fixes brave#7778, fixes brave#5097, fixes brave#6984.
This was referenced Sep 20, 2017
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Did you search for similar issues before submitting this one?
Yes
Describe the issue you encountered:
Enabling Enpass password manager from settings causes the application to hang and close forcefully
Platform (Win7, 8, 10? macOS? Linux distro?):
Windows 10 x64
Brave Version (revision SHA):
Brave 0.13.2
rev fe018d5
Steps to reproduce:
Enpass was not installed while testing this.
Actual result:
Browser hangs
Expected result:
Should enable password manager if app is installed, if app is not installed should do nothing
Will the steps above reproduce in a fresh profile? If not what other info can be added?
Yes
Is this an issue in the currently released version?
NA
Can this issue be consistently reproduced?
Yes
Extra QA steps:
1.
2.
3.
Screenshot if needed:
Any related issues:
The text was updated successfully, but these errors were encountered: