07-13-2021, 10:14 PM
To avoid a double scrollbar, you have to get everything right. It's really annoying. Sometimes you just want to set an "overflow: hidden" in the right place to get rid of the scrollbar ... which works some of the time, but it's better to avoid it if you can. Basically you have to decide what widget is controlling the scrollbar and everything either needs "height: 100%" (or smaller) or an explicit calc setting that will not produce a scrollbar. It will cascade well if everything is set up correctly.
In this case, we need to be able to set the height of the scroll in TableLayoutWdg to fit the view it is in. I think this is what Diego is talking about. The question is whether this should be done externally by specific class or by a kwargs into TableLayoutWdg. Before we had tried to do this with "window_resize_offset" kwarg, but this used a resize event. This worked, but the calc css is much faster and better.
We do have a specific class on the scroll, but it has a hard coded height to 100%
.my_table .spt_table_scroll {
height: calc(100% - 100px") !important
}
The important is set because it is now set to 100%. If this works, then maybe we can find a better solution.
In this case, we need to be able to set the height of the scroll in TableLayoutWdg to fit the view it is in. I think this is what Diego is talking about. The question is whether this should be done externally by specific class or by a kwargs into TableLayoutWdg. Before we had tried to do this with "window_resize_offset" kwarg, but this used a resize event. This worked, but the calc css is much faster and better.
We do have a specific class on the scroll, but it has a hard coded height to 100%
.my_table .spt_table_scroll {
height: calc(100% - 100px") !important
}
The important is set because it is now set to 100%. If this works, then maybe we can find a better solution.