bilogic
bilogic
@ondras don't mean to rush you, but possible to accept this so I can plan my other PRs? Thank you.
Can revert to an earlier version of extension for now?
Is there a way to rollback on Chrome? Which is the culprit actually? Server or browser extension?
@trygveaa did the new release solve the issue? like @flashcode , wanna be sure the issue is actually fixed. :)
@OliverPearmain to test the fix, one would have to build and load the extension unpacked in Chrome.
@travist possible to have this? Thank you.
I realized in the settings of buttons, there is a `POST to URL` option, which solves the problem, but introduces another security related issue of not having CSRF tokens. Instead...
Bug label wasn't added by me. It is more a question.
```JAVASCRIPT builder.instance.form = jsonObject; ```
@paulfalgout Was your issue addressed? The docs say it has to be an object but webform.js itself still uses string. This is getting quite confusing #4862