We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
New yellow “Connection Inactive” state for unready connections.
New user: https://www.figma.com/proto/ltqvnKiejWj0JQiqtDf2JJ/Bitkit-Wallet?page-id=26618%3A121070&node-id=26618-121071&node-type=FRAME&viewport=252%2C96%2C0.13&t=3a2PIK7WZzp5LAls-8&scaling=scale-down&content-scaling=fixed&starting-point-node-id=26618%3A126150&show-proto-sidebar=1&hide-ui=1
Active user: https://www.figma.com/proto/ltqvnKiejWj0JQiqtDf2JJ/Bitkit-Wallet?page-id=26618%3A121070&node-id=26618-126158&node-type=FRAME&viewport=252%2C96%2C0.13&t=VzG6WKLC255EAc0M-8&scaling=scale-down&content-scaling=fixed&starting-point-node-id=26618%3A126154&show-proto-sidebar=1&hide-ui=1
see: https://synonymworkspace.slack.com/archives/C01H106JRQB/p1726065889623369
No response
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Describe the problem
New yellow “Connection Inactive” state for unready connections.
Describe the solution
New user: https://www.figma.com/proto/ltqvnKiejWj0JQiqtDf2JJ/Bitkit-Wallet?page-id=26618%3A121070&node-id=26618-121071&node-type=FRAME&viewport=252%2C96%2C0.13&t=3a2PIK7WZzp5LAls-8&scaling=scale-down&content-scaling=fixed&starting-point-node-id=26618%3A126150&show-proto-sidebar=1&hide-ui=1
Active user: https://www.figma.com/proto/ltqvnKiejWj0JQiqtDf2JJ/Bitkit-Wallet?page-id=26618%3A121070&node-id=26618-126158&node-type=FRAME&viewport=252%2C96%2C0.13&t=VzG6WKLC255EAc0M-8&scaling=scale-down&content-scaling=fixed&starting-point-node-id=26618%3A126154&show-proto-sidebar=1&hide-ui=1
see:
https://synonymworkspace.slack.com/archives/C01H106JRQB/p1726065889623369
Additional context
No response
The text was updated successfully, but these errors were encountered: