Could you please log a ticket through the support channel to have this addressed in the foundation components? Also, kindly include the steps to reproduce the issue.
@dpkhmhsThis issue typically occurs due to slow form rendering, often caused by a large number of form elements or complex custom business rules. Could you please provide answers to the following questions:How many form objects are there in total (i.e., components dropped during authoring)?Are there...
@dpkhmhsBased on the screenshots you shared, it appears you're using foundation components to build the adaptive form. We recommend using the forms core components available through the AEM project archetype for creating adaptive forms.Could you please switch to using the core components for this us...
@SyedWa3The reason for this approach is that the name attribute of each radio button group must be unique. If it's not, the submitted data would be identical for all radio button groups. There are scenarios where forms may include radio buttons with the same name attribute across different panels or...
@dpkhmhsAre you using foundation-based forms or core component-based forms? We've addressed many similar issues to the one you reported with the date picker core component. You can check the component here: https://github.com/adobe/aem-core-forms-components/tree/release/650/ui.af.apps/src/main/conte...
There's no need to import these, as they are already available in the window namespace for foundation forms. You can wrap this invocation once AF is initialized.
The issue could be related to the CORS setup and might be the reason for the 204 response code. Please check if you have a custom com.adobe.granite.cors.impl.CORSPolicyImpl configurationAdditionally, you can enable debug logging on com.adobe.granite.cors to check if it is denying the request.