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
I was looking into #4329 and realized that the power consumption values have incorrect units. It should be Wh and not µWh.
Wh
µWh
The same STR with #4329 can be used for testing.
For example it shows 0.0036 µWh in a report on my machine, but it should be 0.0036 Wh (or better yet, 3.6 mWh).
0.0036 µWh
0.0036 Wh
3.6 mWh
Inside the Firefox Profiler we also have a logic to choose the best unit depending on the value: https://github.com/firefox-devtools/profiler/blob/6306555856f9c5b1f539462f24c182b7c07d477b/src/components/tooltip/TrackPower.js#L84-L115
So this way the unit is always readable/meaningful to the user. But I don't know how easy it is to implement something similar here.
The text was updated successfully, but these errors were encountered:
Hi @canova ooops, thanks! Let me fix that.
Sorry, something went wrong.
Display FF power consumption in mWH #4333
6428905
Display FF power consumption in mWH #4333 (#4334)
6bfd446
No branches or pull requests
I was looking into #4329 and realized that the power consumption values have incorrect units. It should be
Wh
and notµWh
.The same STR with #4329 can be used for testing.
For example it shows
0.0036 µWh
in a report on my machine, but it should be0.0036 Wh
(or better yet,3.6 mWh
).Inside the Firefox Profiler we also have a logic to choose the best unit depending on the value:
https://github.com/firefox-devtools/profiler/blob/6306555856f9c5b1f539462f24c182b7c07d477b/src/components/tooltip/TrackPower.js#L84-L115
So this way the unit is always readable/meaningful to the user. But I don't know how easy it is to implement something similar here.
The text was updated successfully, but these errors were encountered: