Fix two ScrollArea
bugs: leaking scroll target and broken animation to target offset
#4174
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR fixes two issues related to
ScrollArea
.ScrollArea
would havedrag_to_scroll
set tofalse
(e.g. because some custom logic is at play or some other reason), it would not animate to thetarget_offset
, effectively makingResponse::scroll_to_me()
ineffective.ScrollArea
s would leak thescroll_target
's other direction. In certain specific circumstances (e.g. an horizontal area nested in a vertical one, or inversely), this could work as intended, but in many other cases it could cause unwanted effects. With this PR, bothscroll_target
directions are consumed by nearest enclosingScrollArea
, regardless of the actually enabled scroll axes.