Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Configuration should be per-domain #12

Closed
2 tasks
danfinlay opened this issue Mar 7, 2016 · 5 comments
Closed
2 tasks

Configuration should be per-domain #12

danfinlay opened this issue Mar 7, 2016 · 5 comments
Labels
area-background Issues relating to the extension background process. blocked type-enhancement

Comments

@danfinlay
Copy link
Contributor

danfinlay commented Mar 7, 2016 •
edited
Loading

There are some features that are currently plugin-wide, that should actually be configurable on a site-by-site basis.

Please add examples here so we can catch them under this issue:

  • Current RPC
  • Currently visible account
@danfinlay danfinlay added this to the Invite Only Beta milestone Mar 7, 2016
@kumavis kumavis self-assigned this Mar 8, 2016
@danfinlay danfinlay mentioned this issue Mar 22, 2016
Closed
@kumavis kumavis assigned danfinlay and unassigned kumavis Apr 11, 2016
@danfinlay danfinlay modified the milestones: Public Beta, Invite Only Beta Apr 12, 2016
@kumavis kumavis modified the milestones: Public Launch, Public Beta Jun 3, 2016
@danfinlay
Copy link
Contributor Author

This might be more interestingly solved by a method for dapps to declare the network they prefer (which is complicated by the ETC fork). We need to discuss that at some point.

@danfinlay danfinlay modified the milestones: Public Release, Public Beta / DevCon Aug 15, 2016
@danfinlay danfinlay removed their assignment Oct 17, 2016
@danfinlay
Copy link
Contributor Author

I think this is blocked by #328, and we can discuss it after that's resolved.

@danfinlay danfinlay mentioned this issue Nov 8, 2016
Closed
@2-am-zzz 2-am-zzz added P4-someday area-background Issues relating to the extension background process. labels Mar 1, 2018
@2-am-zzz 2-am-zzz removed this from the New UI Public Release milestone Mar 1, 2018
@asymmetric
Copy link

I stumbled upon this issue while reading this article.

Can the issue be worked on, or is it still blocked?

@danfinlay
Copy link
Contributor Author

The important issue addressing concerns like that article is #714.

It's currently under progress, but we are working out a bit of our UX of how to address it (you can see where we're at there).

@bdresser
Copy link
Contributor

Addressed in #714 and assorted issues

danfinlay added a commit that referenced this issue Sep 19, 2019
@danfinlay
Merge pull request #12 from MetaMask/metamask-events
06cc268 
Metamask events
@snyk-bot snyk-bot mentioned this issue Mar 26, 2020
Open
SeungjunWe referenced this issue in DcentWallet/metamask-extension Jul 13, 2020
@vbaranov
Merge pull request #12 from poanetwork/support-poa-network-#2
fe2af9b 
(Feature) Support POA network
meppsilon pushed a commit to meppsilon/metamask-extension that referenced this issue Jan 12, 2022
@dan437
Merge pull request MetaMask#12 from meppsilon/stx-fetch-errors
d46c69e 
Handle fetch errors for stx fees
aloisklink referenced this issue in aloisklink/metamask-extension Jan 19, 2022
Merge pull request #12 from MetaMask/trezor-v6
64426c6 
Upgrade to TrezorConnect v6
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
area-background Issues relating to the extension background process. blocked type-enhancement
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
5 participants
@asymmetric @danfinlay @bdresser @kumavis @2-am-zzz