On Tue, 25 Jan 2022 13:45:54 GMT, Jeanette Winzenburg
wrote:
>> Marius Hanl has updated the pull request incrementally with one additional
>> commit since the last revision:
>>
>> 8277122: Added test for setting a negative divider position + improved
>> readability
>
>
On Tue, 25 Jan 2022 13:38:53 GMT, Jeanette Winzenburg
wrote:
>> Marius Hanl has updated the pull request incrementally with one additional
>> commit since the last revision:
>>
>> 8277122: Added test for setting a negative divider position + improved
>> readability
>
>
> When a divider is moved via drag or code it will call **requestLayout()** for
> the **SplitPane**.
> While this is fine, it is also called when the
> **SplitPaneSkin#layoutChildren(..)** method is repositioning the divider.
>
> This makes no sense since we are currently layouting everything,
On Wed, 26 Jan 2022 05:36:07 GMT, meghanEmbrace wrote:
>> With a touch-enabled device, the scrollbar disappears a short while after
>> it's used. During the layout, updateHbar() checks the hbar visibility and
>> resets the clip, causing the user to be scrolled fully to the left when
>> trying
On Wed, 26 Jan 2022 05:36:07 GMT, meghanEmbrace wrote:
>> With a touch-enabled device, the scrollbar disappears a short while after
>> it's used. During the layout, updateHbar() checks the hbar visibility and
>> resets the clip, causing the user to be scrolled fully to the left when
>> trying
On Wed, 26 Jan 2022 05:36:07 GMT, meghanEmbrace wrote:
>> With a touch-enabled device, the scrollbar disappears a short while after
>> it's used. During the layout, updateHbar() checks the hbar visibility and
>> resets the clip, causing the user to be scrolled fully to the left when
>> trying
