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
Merge recent MRs #139
Merge recent MRs #139
Commits on Sep 6, 2021
-
fix: chart constantly jumping in 1-2 pixel steps
The issue is noticeable at `millisPerPixel` being between ~ 0.5 & 2.0 the size of `requestAnimationFrame` period. Canvas image update period would be inconsistent - some would last longer, some less, some would get skipped altogether.
-
Commits on Sep 7, 2021
Commits on Sep 22, 2021
Commits on Sep 24, 2021
Commits on Sep 28, 2021
Commits on Oct 6, 2021
Commits on Oct 7, 2021
-
-
perf: don't access
canvas.clientWidth
on eachrender()
This changes behavior a bit - when `render(` is passed a canvas different from `this.canvas`
-
-
Commits on Oct 8, 2021
-
fix:
this.delay
not being respected withnonRealtimeData: true
and when the user calls `render` manually with a custom `time` argument
-
-
-
-
fix: series fill & stroke being inconsistent for last data time < ren…
…der time It would depend on `scrollBackwards` and `fillStyle` being `undefined` or not. Depending on this, it would either continue the line up to the edge of the canvas or leave it at `lastX`. This makes it so that it is always left at `lastX`.
-
Commits on Oct 24, 2021
-
perf: Revert "perf: remove unnecessary
context.save()
& `context.res……tore()`" This reverts commit f7b488e. For some reason in Chromium 95.0.4638.54 (and maybe others) that change caused `render()` CPU time to grow over time. For me on the `examples/example1.html` page it would grow from 0.5ms to 50ms over 5 minutes
-