bitshares / bitshares/bitshares-ui
Staging testing - not seeing 'view mode' when not logged in
- Dominant language
- JavaScript
- Stars
- 520
- Forks
- 575
- Avg merge
- 12h 7m
- Merged PRs (30d)
- 5
Description
**Describe the bug**
When I navigated to the [staging environment](https://staging.bitshares.org/#/), I was not logged in and so most of the 'burger' side menu was blanked out.
I clicked on 'voting' which showed '404 page not found' due to not being logged in.
I added a known account name directly to the URL to get past the 404 error.
The web wallet now has this account name in the top bar without the 'view mode' button which is shown when you're logged in but are viewing another user's account (so you don't get confused & to enable returning to your account's view).
As a non-logged-in user, I'm not getting the 'view mode' notice nor have an option to return to being fully anon/logged-out.
**To Reproduce**
Steps to reproduce the behavior:
* Launch the staging client without past history using it (fully logged out).
* Go to blanked out voting link, get 404 voting page
* Edit url directly to add the missing account name to see voting information
* Now the client believes this is your main account & doesn't acknowledge 'view mode'
**Expected behavior**
Show details of null-account when navigating to pages when completely logged out, instead of showing 404 error? So you can view what the latest worker proposals are as a fresh unregistered user.
**Desktop (please complete the following information):**
Windows, firefox, staging 'BitShares.190207-rc2'
Contributor guide
Research direction
Start by reproducing the issue in the staging client from the blanked-out voting link, then inspect the route and account-view handling reached after adding an account name to the URL. Done means a fully logged-out user can access the voting information without a 404 and is clearly shown an anonymous or view-mode state rather than being treated as the account owner.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, react
- Domain
- blockchain, frontend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100