-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
Labels might be cut off when disabling scale and scroll #947
Comments
maxbethke
changed the title
Labels might be cut off when disbaleing scale and scroll
Labels might be cut off when disabling scale and scroll
Dec 20, 2021
timocov
added
enhancement
Feature requests, and general improvements.
good first issue
Good issue for first-time contributors.
labels
Dec 29, 2021
The fix should be somewhere here - we need to respect disabling scrolling/scaling as well, not just fixing an edge. |
timocov
added
the
help wanted
Asking for outside help and/or contributions to this particular issue or PR.
label
Dec 29, 2021
@maxbethke would you like to create a fix for this? |
@rchvalbo no, I don't think so. Please create another ticket for that. |
timocov
removed
help wanted
Asking for outside help and/or contributions to this particular issue or PR.
good first issue
Good issue for first-time contributors.
labels
Jan 14, 2022
3 tasks
Sorry, gotcha too late. Would have loved to help. @timocov |
@maxbethke no worries, we handled it. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Lightweight Charts Version: 3.7.0
Steps/code to reproduce: refer to this codesandbox https://codesandbox.io/s/unruffled-benz-z9f5p
Actual behavior: The last label on the time axis will be hidden behind a non-transparent canvas, if it happens to overflow the canvas for the time scale
Expected behavior: The time scale labels would be overflowing their canvas, so they would display their whole content
Screenshots:
CodeSandbox/JSFiddle/etc link: https://codesandbox.io/s/unruffled-benz-z9f5p
With reference to
#226 and #835
The text was updated successfully, but these errors were encountered: