Skip to content
New issue

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

[1] Max supply bug in Chrome #479

Closed
rwynden opened this issue Oct 1, 2017 · 5 comments
Closed

[1] Max supply bug in Chrome #479

rwynden opened this issue Oct 1, 2017 · 5 comments
Assignees
Labels
[3] Bug Classification indicating the existing implementation does not match the intention of the design
Milestone

Comments

@rwynden
Copy link

rwynden commented Oct 1, 2017

the way to recreate this likely Maximum Supply bug is this: 1) just enter a huge max supply (100... the largest you can). 2) then change the number of decimal points to 8, now 3) max supply will no longer be editable. 4) if you select it and wipe it out, when you re-enter the value you will be restricted to a much smaller max supply

Or... just watch this movie of the interaction... tx
https://www.useloom.com/share/55f57a2e79c8416c9a2f4009ca089ec1

@rwynden
Copy link
Author

rwynden commented Oct 1, 2017

Also... once this has happened another issue crops up:

the SmartCoin and Binary Prediciton Market buttons disappear when you hover over them. they still work, but the user experience is rather funky when that happens, because you can't see the toggle

@rwynden
Copy link
Author

rwynden commented Oct 1, 2017

I am using Chrome Canary
Version 62.0.3171.0 (Official Build) canary (64-bit)

@rwynden
Copy link
Author

rwynden commented Oct 1, 2017

Note: In the video, please note that i started with a number that exceeds the allowed limit, and that displays the correct error message. --> but then i adjusted the decimal places, and later tried to edit the max limit ... that's when the bug happens, the max limit is frozen at a low value.

@wmbutler wmbutler added the [3] Bug Classification indicating the existing implementation does not match the intention of the design label Oct 1, 2017
@wmbutler wmbutler changed the title Max supply bug in Chrome [1.5] Max supply bug in Chrome Oct 1, 2017
@wmbutler wmbutler added this to the 171015 milestone Oct 1, 2017
@calvinfroedge
Copy link
Contributor

@wmbutler @rwynden en How about picking an arbitrary max supply which is known to not cause issues? Open to suggestions.

@wmbutler wmbutler changed the title [1.5] Max supply bug in Chrome [1] Max supply bug in Chrome Oct 13, 2017
@wmbutler
Copy link
Contributor

This is a really strange bug. It's not serious but it is, in fact, a bug. There must be a reason for the maximum digits. I'm not sure if it's a combination of precision and integer or not, but @xeroc can tell us what the limits of issued shares are. Once we know this, I think it's an easy bug fix. There is no reason the Maximum Supply field should become un-editable.

@svk31 svk31 self-assigned this Oct 13, 2017
@svk31 svk31 closed this as completed in 37f6013 Oct 13, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
[3] Bug Classification indicating the existing implementation does not match the intention of the design
Projects
None yet
Development

No branches or pull requests

4 participants