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

Series area stack: huge "peak" values causes smaller values not rendered when zoomed in #7555

Closed
lebnic opened this Issue Dec 19, 2017 · 4 comments

Comments

Projects
None yet
3 participants
@lebnic

lebnic commented Dec 19, 2017

Expected behaviour

When zooming on portions of the graph "away" from the huge peak values, normal smaller values should be rendered accurately. Here, a "peak value" of 999999 was used for each series area
image
image
image

Actual behaviour

When "huge peak values" are used (here we used 491913125223966660), small series area values are not all visible when zoomed in
image
image
image

Live demo with steps to reproduce

http://jsfiddle.net/lebnic/3h30s0v6/

Affected browser(s)

Chrome

@TorsteinHonsi

This comment has been minimized.

Show comment
Hide comment
@TorsteinHonsi

TorsteinHonsi Dec 20, 2017

Collaborator

Same as #3201, it happens because the path goes too far outside the viewport. It also happens in Firefox, but only for the area and not the graph itself.

Collaborator

TorsteinHonsi commented Dec 20, 2017

Same as #3201, it happens because the path goes too far outside the viewport. It also happens in Firefox, but only for the area and not the graph itself.

@TorsteinHonsi TorsteinHonsi self-assigned this Dec 20, 2017

@TorsteinHonsi TorsteinHonsi added the Bug label Dec 20, 2017

@lebnic

This comment has been minimized.

Show comment
Hide comment
@lebnic

lebnic Dec 20, 2017

@TorsteinHonsi , is a fix expected for this issue ? Actually, is commit a26ca3c THE fix ?

lebnic commented Dec 20, 2017

@TorsteinHonsi , is a fix expected for this issue ? Actually, is commit a26ca3c THE fix ?

@pawelfus

This comment has been minimized.

Show comment
Hide comment
@pawelfus

pawelfus Dec 20, 2017

Contributor

Hi @lebnic - you are right, it's fixed in a26ca3c commit. You can check the fix in action here: http://jsfiddle.net/BlackLabel/3h30s0v6/6/

Contributor

pawelfus commented Dec 20, 2017

Hi @lebnic - you are right, it's fixed in a26ca3c commit. You can check the fix in action here: http://jsfiddle.net/BlackLabel/3h30s0v6/6/

@lebnic

This comment has been minimized.

Show comment
Hide comment
@lebnic

lebnic Dec 20, 2017

You guys are awesome! thanks !

lebnic commented Dec 20, 2017

You guys are awesome! thanks !

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