angular icon indicating copy to clipboard operation
angular copied to clipboard

[BUG] WebformBuilder.saveComponent event Issue with Angular 15

Open chakshutadesai opened this issue 2 years ago • 2 comments

Environment

Please provide as many details as you can:

  • Hosting type
    • [ ] Form.io
    • [x] Local deployment Version: Windows 11
  • Formio.js version: 5.5.0-rc.9
  • Frontend framework: Angular 15.1.5
  • Browser: Chrome
  • Browser version: Version 110.0.5481.177

Steps to Reproduce

  1. Drag any component from the form builder (i.e. Text Field)
  2. set properties
  3. click on the save button to save the component on Form.
  4. On click on save button, getting console errors

Expected behavior

SHould not give any errors, and save component on Form.

Observed behavior

On click save button , gives console errors image image

Example

If possible, please provide a screenshot, live example (via JSFiddle or similar), and/or example code to help demonstrate the issue.

For code or form JSON, please enclose in a code block:

// your code here

chakshutadesai avatar Feb 24 '23 13:02 chakshutadesai

We are on angular 14.2.1 and also see this. I haven't been able to reliably reproduce it. I've only seen it twice on my machine which is a mac m1; my coworkers encounter it daily and they are on older windows laptops, so my best theory is its a timing/async issue related to angular event handlers and zones.

https://github.com/formio/angular/blob/master/projects/angular-formio/src/components/formbuilder/formbuilder.component.ts#L94

closesimple-mf avatar Mar 28 '23 16:03 closesimple-mf

@chakshutadesai we cannot reproduce the issue. You can check our demo repository with the latest @formio/angular version https://github.com/formio/angular-demo. Maybe you missed some configuration. Please provide some example in JSFiddle or CodeSandbox for future investigation. Thanks!

roma-formio avatar Apr 27 '23 13:04 roma-formio

Thank you for your contribution. As this issue has been inactive for over 90 days, I will close it for now. If you'd like to reopen the issue, please reply and we can resume the triage process.

olgabann avatar Sep 04 '24 13:09 olgabann