Issue when using a ComboBox as an Editor for a GridInlineEditing instance

Required Information

Version(s) of Ext GWT
«Ext GWT 3.0.6»

Browser versions and OS(and desktop environment, if applicable)

«Internet Explorer 9, Windows 7 Ultimate»

«Firefox 23, Windows 7 Ultimate»

«I think any other browser»

Virtual Machine
«No»

Description
When a ComboBox instance without a custom PropertyEditor is added to a GridInlineEditing instance, then the item which is currently selected remains hightlighted even when the mouse hovers over the other items from the item list.

But it is still possible to select an item from the item list, even that the item
under the mouse pointer is not highlighted.

Run mode
I tested in development mode only. I assume it will also occur in production mode

Steps to reproduce the problem

Create a Grid instance

Create a GridInlineEditing instance

Add a ComboBox without some items in the ListStore without setting a custom PropertyEditor

Connect the GridInlineEditing instance with the Grid instance

Open the editor and try to highlight items by hovering other them

Expected result
That items unter the mouse pointer are highlighted.

Actual result
That the already selected item remains highlighted even that the mouse hovers over other items.

Test case
Apply this patch to your Examples project and try it out for yourself

Helpful Information
The incorrect highlighting seems to have been introduced by the addition of the startMonitoring() method of the AbstractGridEditingclass which perodically calls the method parse() of the default PropertyEditor class of the ComboBoxCell class which calls the selectByValue() method which does the damage.

As a workaround I will try to disable this new feature from all GridInlineEditing instances.

Thanks for the report and sorry for the delay on reviewing this. This appears to have been introduced by the extra validation added to inline editing as you indicated, which apparently causes the field to re-apply its selection.

We'll update this report when we have a fix - for now, turning off the monitoring feature is a good workaround by calling editing.setMonitorValid(false);. This should have been the default for inline editor - our apologies for the oversight.

GridRowEditing

You may already be aware of this as they both inherit from the AbstractGridEditing class, but this issue also occurs with the GridRowEditing class. While the workaround you provided does prevent the issue, it also leaves the Save button enabled when you first add a new row. Usually it is disabled until the user enters the required information.