-
-
Notifications
You must be signed in to change notification settings - Fork 0
feat: support chromium-based Micorsoft Edge #4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Directory structure is similar to chrome
Directory structure is similar to chrome
…into edge_more_platform
Because the keychain was written to death, I don't want to destroy the original code.
Additional Realizations
chrome and edge get a different Safe Storage
reuse chrome's code
kalifun
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
After you changed it, you circled me back. I wanted to do this before. But because of the file name of chrome, I was in a dilemma. That's why it is independent.
If it is more perfect, maybe it should be renamed chromium.
But there is too much dependence. Maybe it is a better solution at present.
| case `chrome`: | ||
| service = `Chrome Safe Storage` | ||
| account = `Chrome` | ||
| case `chromium`: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I haven't tried it, but I understand that they are all based on chromium and their principles should be the same.
Based on #2, thanks @kalifun