I can't recreate the problem.  What browser are you using?

The change you mention is consistent with every other type of event
handling.  It may have exposed another bug somewhere else, but I don't
think it should be considered a bug, itself.

On Mon, Jun 1, 2015 at 3:20 PM, karl ramberg <karlramberg at gmail.com> wrote:
> The scrolling bug is caused by this change:
>
> http://source.squeak.org/trunk/Morphic-cmm.984.mcz
>
> Morph>>handlesMouseMove: anEvent
> "Do I want to receive mouseMove: when the hand passes over the receiver?
> Rules say that by default a morph gets #mouseMove iff
> * the hand is not dragging anything,
> + and some button is down,
> + and the receiver is the current mouse focus."
> ---> self eventHandler ifNotNil: [^ self eventHandler handlesMouseMove:
> anEvent]. <-------
> anEvent hand hasSubmorphs ifTrue: [ ^ false ].
> (anEvent anyButtonPressed and: [ anEvent hand mouseFocus == self ]) ifFalse:
> [ ^ false ].
> ^ true
>
> There seem to be some unintended behavior because of this change.
>
> Karl
>
> On Mon, Jun 1, 2015 at 10:11 PM, karl ramberg <karlramberg at gmail.com> wrote:
>>
>> In latest image the mouse seem to scroll sliders just by mouse over the
>> scroll bar.
>> It's a very unusual behavior, and I think I would like to opt out of it.
>>
>> Is there a preference or is this a bug ?
>>
>> Karl
>
>
>
>
>