Locator fields and pressing [Enter]

[Devan]

Ah, looks like the [Enter] key is going to be the bane of my life today!!

We have a web app which has a section that goes:

Browse List of Orders -> Order Entry Form (with Browse list of Line Items) -> Line Item Entry Form -> Popup of Product List.

The Popup Product List lets the user pick a product code for the Line Item Form obviously.  We also have a search Locator field on this popup which allows the user to filter down to a particular product from the thousands available.

Now, when they type in a partial product description and click the [Search] button, everything works beautifully and the Line Item form is populated with the right product code.

However, when then type in a partial search term and press [Enter], the popup disappears, and the user is placed back TWO procedures before, in the Order Entry Form, and to make matters worse, the Line Item Browse is CLEARED of any pre-existing products - Yikes!!

Great way to nuke all products on your order...not a great way to perform a search.

Anyone else found this?  Any way we can 'trap' the [Enter] key on the locator to prevent this behaviour?

Thanks,
Devan

[kevin plummer]

Hi Devan,

I haven't tried this but what button are you making the default button? Maybe if you set this or add a dummy button which throws an alert and does not close the popup. Anyway just a suggestion...

[Bruce]

I'm using 6.15 here, and I think this was something I updated very recently. Either 6.14 or 6.15. (Obviously you don't have 6.15 yet - I ain't released it yet). but anyway in 6.15 if you press Enter on a locator it just "applies" the locator and resets the browse.

So I think this one is probably sorted.

cheers
Bruce

[Devan]

UPDATE: Bruce, I installed 6.14 and the problem is still occurring.  Which JS file contains the locator autocomplete code, as I might have to make some edits myself here as the client has flagged this as a MAJOR issue when his customers keep losing their orders on the web portal...

Cheers,
Devan