SetFocus to WebRadioGroup or WebDBRadioGroup

When a TWebRadioGroup.SetFocus event executes, the radio buttons in the component do not receive focus.

An alternative works better but still requires the user to tab an extra time.

Can you provide a solution to this issue?

Environment:  Web Core 1.3.3.0 1/14/2020, latest chrome browser in Windows 10 Pro.

Steps to Duplicate:
Create a new TMS Web Application.
Drop a TWebRadioGroup component on the form.
Add Items A,B,C
Increase height so all items are visible.
Drop two TWebEdit components on the form.
In the form's OnShow event:  WebRadioGroup1.SetFocus;
Run the program.

Without using the mouse:
Initial focus seems to be on the TWebRadioGroup but the radio buttons are not selected.
Hitting the tab key follows this sequence.
WebEdit1
WebEdit2
First Radio Button in WebRadioGroup1
Browser downloaded files
Browser downloads open arrow
Browser downloads Show All button
Browser downloads X
Browser view sites information
Browser URL entry area
WebRadioGroup1 but Radio Buttons cannot be changed

Follow these steps to create an alternative that works better but still has an issue:
Create a new TMS Web Application.
Drop a TWebPanel on the form and make it larger.
Drop three TWebRadioButton components on the panel.
Set GroupName on all RadioButtons to 'TEST'
Drop two TWebEdit components on the form below the panel.
In the form's OnShow event:  WebPanel1.SetFocus;
Run the program.

Without using the mouse:
Initial focus is on the panel.
Tab will move to the first Radio Button but its value is not changed when you navigate off.
Afterward, everything works correctly.

Summary
SetFocus does not function as expected with TWebRadioGroup and TwebDBRadioGroup.  The alternative I described works better but still has an issue.

In the alternative, it is possible to use WebRadioButton1.SetFocus in the form's onShow event but you still must use the extra tab.  This appears identical to the problem I described for TWebCheckBox.

Additional Information
The TWebRadioGroup and TWebDBRadioGroup have other issues.  These components do not have TabOrder and TabStop properties. The only event available is onChange which limits what can be done.


We have applied improvements for this issue that will be included in the next update.