Describe the problem
In the documentation in the section "Sticky table modifiers" it is first talked about the z-order of the header. After that follows the seciont "Composable: sticky column" it is described that you have to wrap the table with OuterScrollContainer and Inner ScrollContainer"
The fact, that you need those containers also, when you use "isStickyHeader" is only seen/described further down the documentation in the section "Composable: Sticky columns and header" (At first it sounds like you need the Containers only, if you have sticky columns AND header.
If you do not add the containers in the case of sticky headers only, scrolled tables look weird.
I think the containers should be mentioned earlier in the documentation, already in the section "Sticky table modifiers", when there is the long discussion about the z-order of the header.
Expected behavior
Make the need for InnerScrollContainer and OuterScrollContainer more clear at an earlier location in the documentation.
Is this issue blocking you?
no
What is your environment?
- OS: macOS
- Browser chrome, firefox
- Version 2022.06
Describe the problem
In the documentation in the section "Sticky table modifiers" it is first talked about the z-order of the header. After that follows the seciont "Composable: sticky column" it is described that you have to wrap the table with OuterScrollContainer and Inner ScrollContainer"
The fact, that you need those containers also, when you use "isStickyHeader" is only seen/described further down the documentation in the section "Composable: Sticky columns and header" (At first it sounds like you need the Containers only, if you have sticky columns AND header.
If you do not add the containers in the case of sticky headers only, scrolled tables look weird.
I think the containers should be mentioned earlier in the documentation, already in the section "Sticky table modifiers", when there is the long discussion about the z-order of the header.
Expected behavior
Make the need for InnerScrollContainer and OuterScrollContainer more clear at an earlier location in the documentation.
Is this issue blocking you?
no
What is your environment?