Problem with locator field (NetTalk 6)

[Matthew]

For the position locator:
When entering values, ​​after each character typed, the browser is refreshed and the field is cleaned up, so I can't type more than one character.

For the contains locator:
When entering values, after each character typed, cursor moves to the beginning of that field
(field isn't cleaned up). So for example when I try to search string 'old', search value is 'dlo' and no record is found.

In NetTalk 5 it works ok - browser is refreshed after locator field lost focus.
This problem accours on version 6.

Tested on example 21

Regards,
Matthew

[Bruce]

Hi Matthew,

I opened example 21 and compiled it.

(One thing to note is that this example hasn't been "upgraded to NT6" yet, so it looks a bit funny, but I don't think that's affecting anything.)

the BrowseCustomers procedure has a Position Locator - if you select a sort column (I picked name) then the locator appears. I typed in a name (pay) - pressed tab - and it went to that position. I then typed bay, and again it only jumped back when I tabbed off the field. This was on the desktop (not mobile) using the FireFox browser.

I then went to the app, to the BrowseProducts procedure, and changed the locator there from "Position" to "Contains". Running the app I tested that with various entries, and again it seemed to work as expected.

So, in short, I'm not seeing either effect that you mentioned. I'm not sure if I'm doing it the same as you though, so please tell me more...

Cheers
Bruce

[Matthew]

You were right Bruce.

On FireFox and Chrome and IE that locators works perfect which I didn't check before.

Problem is with Opera browser version 11.60.

Regards,
Matthew

[Bruce]

Hi Matthew,

yes, this appears to be related to the way Opera handles the Change Event. With all other browsers there's a single change event when you "complete" the field - with Opera there's a change event being generated for every keypress. I'll have to think about it, but I don't think there's any "obvious" way of fixing this.

Probably the best approach is to kill the "change" event completely, and then rely on a "search" button to apply the locator. But as I say I'll need to think about it a bit.

cheers
Bruce

[Bruce]

Hi Matthew,

I think I've narrowed down the scope of the problem in Opera.

I've reported the bug to Opera (bug number DSK-355004) but unfortunately there's no way to track the progress of a bug, or determine if it has been fixed. Indeed the Opera FAQ has this to say;
================
Q. Where can I view the status of the bug I reported?
A.  Unfortunately, this information is not publicly available. Fixed bugs are typically described in the changelog for each snapshot. It's possible that the fix will not be listed, so periodic retesting is advised.
================

On the up side I can generate locators slightly differently in Opera, making them type="input" rather than type="search". This means that the search boxes aren't identified as such under Opera, but at least they'll work.

That change will be in the 6.15 build.

Cheers
Bruce