Focus not in item navigated to after mouse click
687325Feb 25 2009 — edited Feb 26 2009Hi,
We have moved a custom Form from 6i to 10g. This form works perfectly fine in the older instance.
However, in R12 we're facing this problem.
When the form opens, the control is on a radio group which has 3 buttons, one of which is hidden. The hidden button is the one that is selected by default. This is to done so that none of the displayed radio buttons are selected by default and the user is forced to select one. Only when he does so, he can proceed to enter the remaining fields.
There is a text item attached to an LOV which is the first text item on this form next to the radio group. The WHEN-NEW-ITEM-INSTANCE trigger for this text item checks if one of the visible radio buttons have been selected, if not, it throws a message to select one and the focus goes back to the radio group.
However, in R12, when I click on the text item, the WHEN-NEW-ITEM-INSTANCE trigger does not fire at all. When I check in diagnostics, the control is still on the radio button, even though the cursor shows it is on the text field. Thus when I try to click on the LOV for the text field I get a "Field does not understand operation error" as the focus is not really on the text field.
If I tab out, then the focus DOES go to the text item and the WHEN-NEW-ITEM-INSTANCE trigger fires, displaying the message as expected. But again, the cursor is still positioned on the text item and not on the radio group. This may prompt the user to click on the LOV field again for the text item.
Since the same code works perfectly fine in our 11.5.9 instance, i was wondering if this is a problem related to R12?
Has anyone faced a similar problem? Any pointers in this regard would be greatly appreciated.