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

Time scales not working #3892

Closed
jugger87 opened this issue Feb 10, 2017 · 8 comments
Closed

Time scales not working #3892

jugger87 opened this issue Feb 10, 2017 · 8 comments

Comments

@jugger87
Copy link

Hello,

The bug is simple, the time scale is not working in the new releases (tested with 2.4.0 and latest 2.5.0), while it works with oldest versions like 2.0.2.

You can see the working example here: http://jsfiddle.net/prfd1m8q/

If you use the new verions with the exact same code it doesn't work.

@etimberg
Copy link
Member

Seems to work ok when the position of the axis is explicitly set http://jsfiddle.net/py1bpf02/

@jugger87
Copy link
Author

Hello etimberg,

I don't knwo if its a problem with my pc, but in you link I cannot see the graphic neither.
I attach a screenshot of your link.

Thanks for the response

sin titulo

@etimberg
Copy link
Member

Weird, it's not working now but I definitely got it working on my phone. I'll take a look when I'm at a computer

@etimberg
Copy link
Member

My fiddle had an error with the position set to ' bottom' instead of 'bottom'. Not sure what the issue is.

@jugger87
Copy link
Author

Hello,

Indeed I think the problem was the white space in the bottom declaration.

Change position:' bottom', for position:'bottom', and It should work.

Thank you very much for the quick answer.

@etimberg
Copy link
Member

👍

I've opened a PR to automatically correct the position for axes if it's wrong. For example, if an x axis has position 'left' that will be updated to 'bottom' to avoid these kinds of problems

@etimberg
Copy link
Member

PR in #3893 was merged to automatically correct axis positions that are knowingly wrong

@ghost
Copy link

ghost commented Aug 2, 2017

I've recently come across this bug and it appears to still be an issue in IE 11 with version 2.6.0.

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

No branches or pull requests

3 participants