[tree view][docs] Fix scroll demos disorientation #13909
Merged
Conversation
This file contains 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
oliviertassinari
added
docs
|
Deploy preview: https://deploy-preview-13909--material-ui-x.netlify.app/ |
flaviendelangle
approved these changes
Jul 22, 2024
oliviertassinari
added
the
design
DungTiger
pushed a commit
to DungTiger/mui-x
that referenced
this pull request
Jul 23, 2024
thomasmoon
pushed a commit
to thomasmoon/mui-x
that referenced
this pull request
Sep 9, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
I got confused playing with the demo of https://mui.com/x/react-tree-view/simple-tree-view/items/#imperative-api. I clicked on the button and got lost, it took me to click 2 more times on the button to understand this demo.
Before
Screen.Recording.2024-07-20.at.11.34.29.mov
After
Screen.Recording.2024-07-20.at.11.35.01.mov
Off-topic. @samuelsycamore I think this could be a small example of work / responsibility we could envision to structure to "Docs" team to grow around, meaning to be accountable for the end-to-end experience of the docs.