UI: bandwith stats have the colors the wrong way around
See original GitHub issueI’m on Revision 1ed2020
, and I just noticed on the Status tab of the webUI the colors for inbound/outbound traffic differ:
- “Network Traffic” shows inbound in orange, outbound in blue
- “Bandwidth over time” shows inbound in blue, outbound in orange
those should probably be swapped so they match up for easier recognition at a glance.
Issue Analytics
- State:
- Created 5 years ago
- Comments:5 (2 by maintainers)
Top Results From Across the Web
States - Material Design
Disabled states are displayed at 38% opacity of the enabled state. Disabled states can also indicate they are not interactive through color changes...
Read more >Designing States for Buttons & UI Interactions | Adobe XD Ideas
Explore the different types of button states and how to design and use them in ways that improve the end-user experience and add...
Read more >How to Choose Colors for Data Visualizations - Chartio
Here, we will highlight some of the simplest tools to help you get up to speed on color choices. ColorBrewer. Screenshot of the...
Read more >Designing UI with color blind users in mind | Secret Stache
Color plays an integral role in UI design. When done right, it improves user experience, influences purchasing decisions, and reflects the brands voice....
Read more >Top 10 Application-Design Mistakes - Nielsen Norman Group
UI elements or controls that move around, violating spatial consistency. An architect in our study who had many years of experience using ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Well, what’s happening is that you’re using the latest “production” version of
go-ipfs
which has a specific version of the Web UI (the one you’re using).With every release of the Web UI we PR the repos that use it, such as
go-ipfs
(https://github.com/ipfs/go-ipfs/pull/5855, https://github.com/ipfs/go-ipfs/pull/5899, https://github.com/ipfs/go-ipfs/pull/5928), but then it’s up to those repos to be released so you can access the newest Web UI through them.So, the next version of
go-ipfs
will already have the newer Web UI!@fsdiogo actually, that’s also the latest release on dist.ipfs.io and the go-ipfs github repo, am I missing something here? 0.o
EDIT: ok, found the problem, makes sense, the webui vs daemon are updated independently, and https://github.com/ipfs/go-ipfs/blob/master/core/corehttp/webui.go#L4 is still not a ipns address.