Putting a ScrollingFrame inside another ScrollingFrame does not work if the nested ScrollingFrame has scrolling direction set to X instead of Y.
Using MacOS Ventura and tested in Studio.
The attached repro file should illustrate the issue well. The ScrollingFrames that have green and black boxes work fine, but the ScrollingFrame with the red boxes does not work. The only difference is the scrolling direction.
The horizontal scrollingframe works if the parent scrollingframe has canvassize set to 0. I can also drag the scrollbar manually but scrolling with touchpad/scroll wheel does not work.
Any updates on this? Im having the same issue on windows. Where a horizontal scrolling frame inside a vertical wont scroll unless i hold left shift. It does work if the “interior” scrolling frame is vertical, but not if horizontal
Hi this is still a problem. As you can see if the nested scrolling frame moves vertically it works as expected, but when I change it to scroll horizontally the scroll wheel ignores the nested scrolling frame even though my mouse is over it.
Hi folks, this behavior is actually intended by design. It prevents players from accidentally scrolling horizontally when the scrolling frame is nested inside another vertical scrolling container.
However I see the point of this request. I’m wondering if at some point we should consider exposing a new API or property that allows creators to explicitly control or override the nested scrolling behavior.
I ended up keeping track of if a mouse was over the frame holding the horizontal scrolling frame, and if it was i’d temporarily change the vertical scrolling frames scrolling property to horizontal
I must ask, since a horizontal scrolling frame would only ever be inside a vertical scrolling frame by intention, then why design it to not work? To stop accidentally scrolling, the decision was to do something that prevents intentional scrolling? But then there isn’t a point in having the horizontal scrolling frame inside a vertical one, so it gets removed, so there is no longer anything to protect against…
Agree with this. You guys mentioned it’s intentional that it doesn’t work, but if a developer intentionally puts a horizontal scrolling frame inside a vertical scrolling frame I can’t see why they wouldn’t want that to work.
I should also mention that it actually works on mobile and console, it’s only scroll wheel input that is ignored.
If a developer didn’t want the horizontal SF to work they could just disable it themselves?
Fyi, this was the use case I had for this functionality. I ended up just doing a little hacky solution where I added an invisible vertical scrolling frame over the horizontal scrolling frame then just mapped the position of the dummy vertical one to the horizontal one. (Only needed for desktop)