keybase / keybase/keybase-issues
Replace DNS proof in browser results in JavaScript error
Open
- Dominant language
- No language data
- Stars
- 899
- Forks
- 40
- PR merge metrics
- No merged PRs in 30d
Description
I don't have a saved private key in the interface, so I think it should have shown a message saying that I need to do it on the command line. I already did so, so I no longer have the browser consul error. :(
It failed on macOS 10.12 (High Sierra) with both current Safari and Chrome.
Contributor guide
No contributing guide indexed for this repository
Research direction
No source file or test is named. Start by reproducing the browser result in Safari or Chrome on macOS when no private key is saved, then trace the DNS-proof flow. Done means the browser shows a clear message directing the user to perform the operation on the command line instead of producing a JavaScript error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, macos
- Domain
- frontend, web-dev
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100