This provides (possibly much) faster Vscrolling. Relates to #31, #38, and #60.
@r4j4h if you have any thoughts, I would be interested to hear them. E.g., commit 1ab36fac79408840bacf46d78808cb76a2622f7a and its parent commit 88017aec3330a4ba62e41c9ef5ef780ad5a0bb80. Using position:relative means we never have to change the V position of the div.tf-action-groups manually, so vscroll_function is gone. However, it does mean we have to change the H position when the window is resized horizontally or scrolled horizontally (the latter is not yet implemented), or when the V scrollbar appears or disappears. Since the only feedback I have received is that running with the H scrollbar hidden is popular :) , I'm not too worried about H scroll speed.
This provides (possibly much) faster Vscrolling. Relates to #31, #38, and #60.
@r4j4h if you have any thoughts, I would be interested to hear them. E.g., commit 1ab36fac79408840bacf46d78808cb76a2622f7a and its parent commit 88017aec3330a4ba62e41c9ef5ef780ad5a0bb80. Using
position:relativemeans we never have to change the V position of thediv.tf-action-groups manually, sovscroll_functionis gone. However, it does mean we have to change the H position when the window is resized horizontally or scrolled horizontally (the latter is not yet implemented), or when the V scrollbar appears or disappears. Since the only feedback I have received is that running with the H scrollbar hidden is popular :) , I'm not too worried about H scroll speed.