ComboTree - Panel problem when scrolling on the outside area

[amir-t]

Hi,
In case the comboTree contained inside scrollable div, and its panel is opened -
when we move the mouse cursor outside the comboTree's bounds, but inside the scrollable panel's area,
and try to scroll with the mouse wheel, the comboTree panel will move in relation to the scrolling direction instead of being closed.

You can see this problem in the following test:
http://jsfiddle.net/xFy42/23/

Here is the steps in order to reproduce the problem:
1. Open the comboTree panel.
2. Move the mouse cursor outside of the opened panel, but still inside the parent panel area (the blue area).
3. Start moving the mouse wheel in order to scroll the parent panel, and the comboTree's panel will move with it instead being closed. As you can see in the following screenshot:



How can we fix this problem?

Thanks.

[stworthy]

Please try to download the patch from http://www.jeasyui.com/download/downloads/jquery-easyui-1.4-patch.zip.

Or add the following code to the page.

Code:

<script>
	$(function(){
		$(document).bind('mousewheel.combo', function(e){
			$(e.target).trigger('mousedown.combo');
		});
	});
</script>

See this updated example http://jsfiddle.net/xFy42/26/.

[amir-t]

Hi,
Thanks a lot for your fix, the fix is working, but unfortunately, we still have a problem.
The fix works only when the 'comboTree' is already been created when the page is loaded (document ready).
But when trying to create another new dynamic 'comboTree' component on demand,
the creation logics is removing the 'mousewheel' binding for some reason, and the original problem repeats itself.

Please see the following example (you can notice that the fix is working till you try to append new comboTree component):
http://jsfiddle.net/xFy42/29/

Is there a solution for this issue?

[stworthy]

Please try the code below instead.

Code:

<script>
	$(function(){
		$(document).bind('mousewheel', function(e){
			$(e.target).trigger('mousedown.combo');
		});
	});
</script>

[amir-t]

It seems that this fix solved the problem.
thanks!