On Tue, 5 May 2020 16:49:09 GMT, Jose Pereda wrote:
> `VirtualFlow` makes use of `VirtualScrollBar` controls, that are laid out
> next to the clipped container region, by
> default.
> However, when touch is supported, these scrollBars are floating controls laid
> out over the container.
On Tue, 5 May 2020 16:49:09 GMT, Jose Pereda wrote:
> `VirtualFlow` makes use of `VirtualScrollBar` controls, that are laid out
> next to the clipped container region, by
> default.
> However, when touch is supported, these scrollBars are floating controls laid
> out over the container.
On Tue, 5 May 2020 16:49:09 GMT, Jose Pereda wrote:
> `VirtualFlow` makes use of `VirtualScrollBar` controls, that are laid out
> next to the clipped container region, by
> default.
> However, when touch is supported, these scrollBars are floating controls laid
> out over the container.
On Wed, 6 May 2020 23:18:33 GMT, Kevin Rushforth wrote:
>> @aghaisas can you also take a look?
>
> I've asked Ajit to review it (and I presume Johan will review as well?)
>
> It looks like a safe enough fix. Have you tested it on multiple platforms?
Yes, I've tested on Mac OS and Linux (with
On Tue, 5 May 2020 16:49:09 GMT, Jose Pereda wrote:
> `VirtualFlow` makes use of `VirtualScrollBar` controls, that are laid out
> next to the clipped container region, by
> default.
> However, when touch is supported, these scrollBars are floating controls laid
> out over the container.
On Wed, 6 May 2020 23:16:41 GMT, Kevin Rushforth wrote:
>> `VirtualFlow` makes use of `VirtualScrollBar` controls, that are laid out
>> next to the clipped container region, by
>> default.
>> However, when touch is supported, these scrollBars are floating controls
>> laid out over the
`VirtualFlow` makes use of `VirtualScrollBar` controls, that are laid out next
to the clipped container region, by
default.
However, when touch is supported, these scrollBars are floating controls laid
out over the container. Therefore, in
this case, when the viewport dimensions are updated,
