-
-
Notifications
You must be signed in to change notification settings - Fork 1.4k
[charts-pro] Add size for zoom slider #17736
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
Open
bernardobelchior
wants to merge
2
commits into
mui:master
Choose a base branch
from
bernardobelchior:zoom-slider-size
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+76
−16
Open
Changes from all commits
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Large diffs are not rendered by default.
Oops, something went wrong.
Large diffs are not rendered by default.
Oops, something went wrong.
Large diffs are not rendered by default.
Oops, something went wrong.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not sure if it's worth documenting this. I still feel a bit uneasy that we're calling it size, but it only affects the margin.
Should we maybe call it
margin
instead?Another drawback of
size
is that if a user sets a size small than 20, we'll see the slider bleeding onto other elements.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I got confused by this, but now I noticed the slider is an svg element.
I was assuming it to be HTML 🤯
What was the rationale for SVG vs HTML? 🤔
I assumed this interactive part would be easier to handle by having a HTML, since when the preview is added, the scales/drawingarea will have to be recalculated anyways.
This would have the benefit of not having to calculate sizes, but I haven't thought about it too deeply.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I made it SVG because we can have stacked axis on one side and the slider should be next to the axis it represents, so to use HTML meant we'd need to use a
foreignObject
, which I wanted to avoid.Even if we use HTML, we'd need to calculate size because if we have an axis below a zoom slider, we'd need to be observing the sliders size to update the axes' offsets so they wouldn't overlap.
Are you seeing any approach with HTML that makes it simpler to handle this case?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I hadn't thought of it, though I suspect this to be such and edge-case that it might not be worth optimising for it.
WDYM?
If the HTML is in the HTML part of the charts it would behave just like the legend does right now, which is automatic layout.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If we want to have this edge case working properly:
Then we need to offset the second axis by the size of the slider so that they don't overlap.
How could we fix this with HTML?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I just wouldn't solve it. Like, this is already an edge case, it is visually complex for the users to understand too.
It is probably easier both on our and the user side to couple visually similar elements together, and let the users figure out which controls which by using it. We can help by keeping them in order though 😆
If a dev really wants to have them in different order they can play with the axis size and absolute positions. But again, that would be a super edge-case
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah, I agree with this.
Yeah, I can agree with this.
Is it worth converting everything to HTML now, though? I can do it if needed.
@alexfauquette what's your take on this?