<p dir="auto">Example code:<br>
<a href="https://gist.github.com/eseidelGoogle/bc15918be8ff1f473ddb4e755699fdfd">https://gist.github.com/eseidelGoogle/bc15918be8ff1f473ddb4e755699fdfd</a></p>
<p dir="auto">I used a null InputValue, which might be confusing things?</p>
<p dir="auto">Click on the Input and then scroll, note how the cursor doesn't stay stuck to the input value.</p>
<p dir="auto"><a target="_blank" rel="noopener noreferrer nofollow" href="https://cloud.githubusercontent.com/assets/11857803/16781244/26de8750-482f-11e6-9501-4f0f73906fe8.png"><img src="https://cloud.githubusercontent.com/assets/11857803/16781244/26de8750-482f-11e6-9501-4f0f73906fe8.png" alt="flutter_01" style="max-width: 100%;"></a></p>
<p dir="auto"><a class="user-mention notranslate" data-hovercard-type="user" data-hovercard-url="/users/mpcomplete/hovercard" data-octo-click="hovercard-link-click" data-octo-dimensions="link_type:self" href="https://github.com/mpcomplete">@mpcomplete</a></p>
<p dir="auto">Put an Input control inside a Scrollable view and select some text. When you scroll the view, the selection controls (handles and toolbar) don't move.</p>
<p dir="auto">We need some way of informing the selection UI that the Input has been moved. We don't have a generalized way of doing this yet. <a class="user-mention notranslate" data-hovercard-type="user" data-hovercard-url="/users/Hixie/hovercard" data-octo-click="hovercard-link-click" data-octo-dimensions="link_type:self" href="https://github.com/Hixie">@Hixie</a>'s thoughts on the matter:</p>
<blockquote>
<p dir="auto">so yeah, fundamentally the answer to your question is no, widgets (or more to the point, render objects), have no idea if they're being moved. This is an issue with, e.g., Material ink splashes; if you put a button in a rotating animation and the animation in a Material and tap the button, the splash will go all wrong.<br>
we have a workaround for lists specifically, lists bubble a ScrollNotification. but that doesn't help in the general case.<br>
there is a theory that one solution would be to do this at the layer level<br>
we could have a layer that is pinned to the position of another layer<br>
since that's the one tree that we do walk entirely each frame<br>
so then whatever logic you wanted to do could be hooked up to the layer<br>
e.g. if you wanted the selection handles to track the selection, you'd put the text field in a layer, the handles in a layer, and you'd tell the handles layer to track the global position of the selection layer<br>
we don't have any support for this right now. <a class="user-mention notranslate" data-hovercard-type="user" data-hovercard-url="/users/abarth/hovercard" data-octo-click="hovercard-link-click" data-octo-dimensions="link_type:self" href="https://github.com/abarth">@abarth</a> might have ideas for how it should look, he's our layers guy.</p>
</blockquote>