The VSCode Extension does not have great support for scrollable content within a cell output, so we have to implement our own solution for passing wheel events to the cell content vs. the notebook frame. In order to know when a wheel event over a cell should be consumed by the cell vs. the notebook, we need to know about the scroll position of the malloy table. We need to know whether the table is scrolled all the way to the top and/or the bottom. We can use this to then determine in VSCode whether the table has more room to scroll up/down, or if scrolling should resume on the notebook.
The VSCode Extension does not have great support for scrollable content within a cell output, so we have to implement our own solution for passing wheel events to the cell content vs. the notebook frame. In order to know when a wheel event over a cell should be consumed by the cell vs. the notebook, we need to know about the scroll position of the malloy table. We need to know whether the table is scrolled all the way to the top and/or the bottom. We can use this to then determine in VSCode whether the table has more room to scroll up/down, or if scrolling should resume on the notebook.