I have written a simple ‘login’ form as a DSP.
When run in chrome focus is placed in the ‘username’ field.
When run using $widgetoperation("LoadURL",v_url) in a uniface form, with the only visible field being the html widget, (mapped top, bottom, left. right) no field has focus, and tab is required to get focus on the username field.
I have tried setting $prompt to the html field just before the edit command. And using the .focus() property of the name field in a webactivate of javascript at the very end of the exec trigger in the dsp.
Putting an alert in the javascript indicates the focus is set before the ‘placeholder’ values are removed from the data (and the labels etc assigned) so I think that is too early.
Is there a trigger fired when uniface has done all it’s work on populating the fields and labels using ux- or can someone tell me why the behaviour is likely to be different between cefrender and chrome for gettinf the focus in the first place?
Regards,
Iain
