Kevin Chappell

@jgittler yes definitely helpful, thank you. I'll look into spreading the remaining attrs into the attribute field, this would include `required` and should solve the problem.

@suleymantasci sorry just getting to this. Can you explain how this error occurs with steps to reproduce? I don't quite understand the problem or why it only occurs with those...

@mkgn do you know what line of code is triggering that error? formBuilder doesn't use `eval` 

Labels and other text data are saved as strings in the formData. I've been doing a lot of work i18n for future release and think there are a couple options...

@eradin This is excellent. I'm curious as to why the styling is not working in the editor though, perhaps adding specificity to the selector just in the editor would help...

@eradin There are some events but none for the ones you mentioned. There are a number of improvements coming in this area though and they are exposed to an api.

@riverofjanuary is there a reason you cant use the `textarea` type? @eradin you probably already saw it but there is now `onOpenFIeldEdit` and `onCloseFieldEdit` options. https://formbuilder.readthedocs.io/en/latest/formBuilder/options/onOpenFieldEdit/ To your original issue,...

@eradin It sounds like the editor might not be internally saving custom attributes `typeUserAttrs` I'll look into that.

this is a cross-domain permissions issue. you can write a `sessionStorage` wrapper that does something similar to this: https://levelup.gitconnected.com/share-localstorage-sessionstorage-between-different-domains-eb07581e9384 The other option is disable sessionStorage in formBuilder. This should really...

@chenster I mean we should probably add an option to formBuilder like `disableSessionStorage` as formBuilder doesn't rely on it outside of saving the control order which is low priority feature:...