Hi Thierry

When the property of a texBox.wlAlwaysBlur = .F. Object, if no entry is made on the client browser side, no 'BLUR' event is sent to the server. However, for the most part, the opposite is always the case:

• on textbox.readonly = .T. the 'BLUR' event is sent
• on texbox.readonly = .F. and while no keystroke in the field has been made, the 'BLUR' event is transmitted to the server It seems that the only situation in which the 'BLUR' event is not transmitted to the server when there has been no keystroke in a textBox is when the form (parent of the textbox) is in the same state as when the form was initiated (). As soon as a view has been reloaded and the state of the form and its objects is different from the state after the form's init (), the javascript management of the blocking of the 'BLUR' event without typing the keyboard no longer works correctly.

Amicalement

Gilles

Hi Gilles,

What do you have in xxx.js for inputAlwaysBlur and inputAlwaysBlurOnReturn?

Merci Thierry,

in xxx.js (PROD) there is no InputAlwaysBlur propertie there is only :

autoBlurDelay: -1,

inputAlwaysBlurOnReturn: true,

I will test in the local xxx.js by changing inputAlwaysBlurOnReturn: false, also testing with inputAlwaysBlur : false,

Amicalement

Thierry,

Merci.

inputAlwaysBlurOnReturn: flase, fixes the problem. There is no longer any untimely 'BLUR' on read-only 'textBox', nor on the typing of the 'ENTER' key when this has not been preceded by an entry of characters in the 'textBox' field '

I continue to optimize my applications used in WEB mode.

Amicalement Gilles

You can double check all currently available FoxinCloud.js settings in home(1) + "tools\ab\aw\app\site\xxx.js"

New settings may have appeared since you built your app’s xxx.js.

To know the current value of a setting, you can just type FoxInCloud.<setting> in the browser console (case sensitive, however intellisense will help)