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

YTD doesn't disable when All is clicked on the stock chart range selector #5931

Closed
khoomeister opened this Issue Nov 4, 2016 · 1 comment

Comments

Projects
None yet
2 participants
@khoomeister

khoomeister commented Nov 4, 2016

Expected behaviour

https://jsfiddle.net/khoomeister/03ccu53f/3/

If I select All, YTD should be disabled.

Actual behaviour

If I select All, YTD remains enabled. Furthermore, if I then select YTD, All remains enabled.

On the other hand, refresh the page and if I select YTD, All becomes disabled like it should be.

Live demo with steps to reproduce

https://jsfiddle.net/khoomeister/03ccu53f/3/

@jon-a-nygaard jon-a-nygaard added the Bug label Nov 7, 2016

@jon-a-nygaard

This comment has been minimized.

Show comment
Hide comment
@jon-a-nygaard

jon-a-nygaard Nov 7, 2016

Collaborator

@khoomeister Thanks for reporting, we will work on fixing this as soon as possible.

Edit:
_Internal Note: All is not disabled when clicking YTD after the All has been selected. As if the range selector does something special with the last selected button.

Collaborator

jon-a-nygaard commented Nov 7, 2016

@khoomeister Thanks for reporting, we will work on fixing this as soon as possible.

Edit:
_Internal Note: All is not disabled when clicking YTD after the All has been selected. As if the range selector does something special with the last selected button.

@jon-a-nygaard jon-a-nygaard self-assigned this Nov 9, 2016

jon-a-nygaard added a commit that referenced this issue Nov 14, 2016

@jon-a-nygaard jon-a-nygaard added this to the 5.0.3 milestone Nov 14, 2016

jon-a-nygaard added a commit that referenced this issue Nov 17, 2016

TorsteinHonsi added a commit that referenced this issue Nov 17, 2016

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment