Focus with mouseover erases the suggested part of the input field

I wish to define the following behavior on launching the focus event:

• If the suggestion element from the autocomplete's list is focused on using the keyboard- call a predefined function to include the suggestion at a specific place in the input field and do not return false
• If the element is focused using the mouse though- return false to avoid any modifications to the input field.

To accomplish this, i determine the event.which against a keyboard or mouse event (tried this in both directions). The keyboard segment of the if statement works like a charm, but the mouse doesn't:

When i focus on an element from the list with the keyboard, the text is replaced in the input field, but if a focus with the mouse on any element from the list afterwards, the input gets erased with only the original, manually inputted text left.

A somewhat similar behavior could be observed if one does the following in autocomplete's "Accent folding" demo (http://jqueryui.com/demos/autocomplete/):

1. Type in "j"

2. Press the arrow- down key to focus on ''Jörn Zaefferer''- the input field gets updated with the value ''Jörn Zaefferer''

3. Right after that- focus on any element of the list with mouseover- the field gets restored to it's original state, with only the letter ''j'' left

The only way to avoid erasing the field, without changing jQuery UI's code is simply returning false in the focus event, instead of determining events with if/else on event.which. I need the text replacement on keyboard though.

I think i have found a (nasty) workaround: in the function blur on line 6454 of jQuery UI 1.8.16, return false at the beginning, or comment out the whole function:

#!js
blur: function( event, ui ) {

        // my change
	return false;

	// don't set the value of the text field if it's already correct
	// this prevents moving the cursor unnecessarily
	if ( self.menu.element.is(":visible") &&
		( self.element.val() !== self.term ) ) {
		self.element.val( self.term );
	}
}

Since i am very reluctant to change the library's code, i was wondering if anybody could help me out or address the issue. Ticket [ticket:5318] addresses a similar issue, but couldn't help me any further.

Best regards,

Boyan Penev