Hello!

react-beautiful-dnd is no longer being maintained by Atlassian per their readme. It currently doesn't support React 18 and strict mode.

Another developer and myself created a fork @hello-pangea/dnd which improves a few things:

• React 18 support
• React strict mode support
• React redux 8 support
• Converted entire codebase and tests to typescript
• Run test suite with React 16, 17, and 18

@hello-pangea/dnd is a drop-in replacement for react-beautiful-dnd and should require no changes to support aside from renamed imports.

Would Quill Forms be interested in a PR adopting @hello-pangea/dnd instead of react-beautiful-dnd?

It would be really helpful to my application if someone could implement/help me implement some or all of these features:

• A way to allow the final submit button to be activated with the enter key (similar to all the "next" buttons)
• A way for the goToBlock function to be used outside of the onSubmit hook
• An option to switch the functions of ENTER and SHIFT+ENTER (ie. enter makes a new line and shift enter goes to the next block)
• An option for text entry boxes to be disabled (similar to the HTML attribute "disabled")

If any of this is obvious, please send me the documentation to solve it (I couldn't find it on GitHub or the website).

Thank you!

Describe the bug
when using npm run build to generate a production astro build, the following error is returned

file: /Users/sparks/work/intro/community-web/node_modules/astro/astro.js:1:0
1: #!/usr/bin/env node
   ^
2: /* eslint-disable no-console */
3: 'use strict';
transforming (221) node_modules/email-validator/index.js error   Unexpected character '!'
  File:
    /Users/sparks/work/intro/community-web/node_modules/astro/astro.js
  Code:
    1: #!/usr/bin/env node
       ^
    2: /* eslint-disable no-console */
    3: 'use strict';
  Stacktrace:
RollupError: Unexpected character '!'
    at error (file:///Users/sparks/work/intro/community-web/node_modules/rollup/dist/es/shared/node-entry.js:2125:30)
    at Module.error (file:///Users/sparks/work/intro/community-web/node_modules/rollup/dist/es/shared/node-entry.js:13339:16)
    at Module.tryParse (file:///Users/sparks/work/intro/community-web/node_modules/rollup/dist/es/shared/node-entry.js:14016:25)
    at Module.setSource (file:///Users/sparks/work/intro/community-web/node_modules/rollup/dist/es/shared/node-entry.js:13626:39)
    at ModuleLoader.addModuleSource (file:///Users/sparks/work/intro/community-web/node_modules/rollup/dist/es/shared/node-entry.js:23591:20)

  Cause:
SyntaxError: Unexpected character '!' (6:1)
    at Object.pp$4.raise (file:///Users/sparks/work/intro/community-web/node_modules/rollup/dist/es/shared/node-entry.js:20995:13)
    at Object.pp.readToken_numberSign (file:///Users/sparks/work/intro/community-web/node_modules/rollup/dist/es/shared/node-entry.js:22585:8)
    at Object.pp.getTokenFromCode (file:///Users/sparks/work/intro/community-web/node_modules/rollup/dist/es/shared/node-entry.js:22660:17)
    at Object.pp.readToken (file:///Users/sparks/work/intro/community-web/node_modules/rollup/dist/es/shared/node-entry.js:22350:15)
    at Object.readToken (file:///Users/sparks/work/intro/community-web/node_modules/rollup/dist/es/shared/node-entry.js:24816:24)
    at Object.pp.nextToken (file:///Users/sparks/work/intro/community-web/node_modules/rollup/dist/es/shared/node-entry.js:22341:15)
    at Object.pp.next (file:///Users/sparks/work/intro/community-web/node_modules/rollup/dist/es/shared/node-entry.js:22302:8)
    at Object.pp$9.eat (file:///Users/sparks/work/intro/community-web/node_modules/rollup/dist/es/shared/node-entry.js:18226:10)
    at Object.pp$9.semicolon (file:///Users/sparks/work/intro/community-web/node_modules/rollup/dist/es/shared/node-entry.js:18273:13)
    at Object.parseImport (file:///Users/sparks/work/intro/community-web/node_modules/rollup/dist/es/shared/node-entry.js:24964:12)
    at Object.pp$8.parseStatement (file:///Users/sparks/work/intro/community-web/node_modules/rollup/dist/es/shared/node-entry.js:18472:49)
    at Object.pp$8.parseTopLevel (file:///Users/sparks/work/intro/community-web/node_modules/rollup/dist/es/shared/node-entry.js:18353:21)
    at Object.parse (file:///Users/sparks/work/intro/community-web/node_modules/rollup/dist/es/shared/node-entry.js:18125:15)
    at Function.parse (file:///Users/sparks/work/intro/community-web/node_modules/rollup/dist/es/shared/node-entry.js:18175:35)
    at Graph.contextParse (file:///Users/sparks/work/intro/community-web/node_modules/rollup/dist/es/shared/node-entry.js:24622:38)
    at Module.tryParse (file:///Users/sparks/work/intro/community-web/node_modules/rollup/dist/es/shared/node-entry.js:14013:31)
    at Module.setSource (file:///Users/sparks/work/intro/community-web/node_modules/rollup/dist/es/shared/node-entry.js:13626:39)
    at ModuleLoader.addModuleSource (file:///Users/sparks/work/intro/community-web/node_modules/rollup/dist/es/shared/node-entry.js:23591:20)
    ```
**To Reproduce**
Steps to reproduce the behavior:
1. `npm create astro@latest`
2.` npx astro add react`
3. `npm install @quillforms/renderer-core --save`
4. `npm install @quillforms/react-renderer-utils --save`
5. create update index.astro to have a basic form
6. `npm run build`
above error pops up

**Expected behavior**
A clear and concise description of what you expectedstephen to happen.

**Screenshots**
If applicable, add screenshots to help explain your problem.

**Desktop (please complete the following information):**
 - OS: OSX
 - Browser N/A
 - Version v4.2.0 of quillforms-latest. 2.1.3 of astro to latest

**Additional context**
Add any other context about the problem here.

At the moment, Submit Button isn't working with hitting "Enter" only because the user might hit "Enter" thinking that he will go to the next block but the submission will be processed unintentionally. That's why Submit is working with combination of CMD + Enter key together and that's great at the moment but there is no hint for the user to let him know he can process the submission using those keys.
The hint should be different according to the operating system. For mac users, it should be CMD + Enter and for any other PC operating system, it should be ⊞ Win + Enter. For any other mobile operating system, there would be no hint mainly.

Merge tags dropdown has a problem in positioning.
Fix for it is using Dropdown menu WordPress component or Popover instead of using custom portal component.

Describe the bug
Hi, would you please provide example on how to run this as a react app

^^ is what I see when I run yarn dev

Why

• The design is quite nice, copying type form very closely... nothing wrong with this.
• For those that might want to custom style the form outside the simple customCss inputs.

What I have done:

• Created an example that implements Material UI, and it's own navigation
  • Using simple CRA app.
  • All code implemented in TypeScript, including the example block from your docs.
  • A very simple block with MUI support, and navigation.
  • Just a visual example, the navigation implemented is next(), through a MUI button.

Questions:

• Can we get prev(), submit() etc functions exposed in the Quillforms forms API?
• Can we get a setting such as disableQuillformsNavigation instead of my hack:

/* Removes the Quillforms navigation */
.renderer-core-field-footer { display: none; }

• Let me know if you are open these changes, can help implement, thank you.

Here is the console info (I dont have any problem with rest API mydomain.com/wp-json shows output,

POST https://mydomain.com/wp-json/wp/v2/quill_forms?_locale=user 403
Uncaught (in promise) {code: 'rest_cannot_create', message: 'Sorry, you are not allowed to create posts as this user.', data: {…}}

Hi, I need to please get the results for 'NEMISA TV' test survey.

While creating Custom Thank You Screens in my Quillform, at some point the layout options ceased working. I have one Form where they work fine, but when I created a second form, after a certain point of editing the layout options no longer have any effect.

Every new Thank You screen in this Form has the same problem. When I clone the Form, the new Form also has the same problem with existing Thank You screens as well as new ones. However, creating a new Form entirely reverts back to normal behavior.

Expected behavior
The layouts should work.

Screenshots
Video of the editor showing layouts not being applied
https://watch.screencastify.com/v/1SKwRZaPbPb7GiILxukB

Desktop (please complete the following information):

• OS: Win10
• Browser Chrome
• Version 114.0.5735.199

In emails, the merge tags should be processed as well for field labels.

Describe the bug
There is no "Hint" shown on "statement" block and I am not able to move to next step by pressing "enter"

To Reproduce
I created a Form which has some "statement" blocks.
From Frontend, after I reach "statement" block, I am not able to move to next step by pressing "Enter" key

Expected behavior
It should move to next step(block) after I hit "Enter" like other blocks do.

Screenshots
If applicable, add screenshots to help explain your problem.

Additional context
I am doing this in React.
Sandbox Link

I would like a way to autofocus into text blocks (similar to the HTML attribute autofocus).

The form renderer doesn't fully support RTL.

Describe the bug
I am following the documentation and it does not mention the FormObj.hiddenFields property, which is not an optional argument

To Reproduce
Steps to reproduce the behavior:

1. Steps from documentation: https://github.com/quillforms/quillforms/blob/master/react-docs/get-started.md#getting-started
2. Also compilation error can be seen in the example sandbox the documentation provides: https://codesandbox.io/s/quill-forms-example-20uuf?file=/src/App.tsx

Expected behavior

1. The documentation and sandbox should be updated to contain this property and explain how it should be used
2. If not actually mandatory, the code should be updated to have it as optional and prevent compilation errors

Screenshots

Desktop (please complete the following information):
N/A

Smartphone (please complete the following information):
N/A

Additional context
N/A

As the title says, there is a problem with the touch sensitivity in touch screens to swipe up or down.

Hi,

I'm not sure is this right way for translating packages files

For example, case of packages/builder-core/src/components/no-blocks/index.tsx file,

import @wordpress/i18n dependency like below

/**
 * WordPress Dependencies
 */
import { __ } from '@wordpress/i18n';

then can use translate function on this line,

like this

{ __( 'Please insert at lease one block.' ) }

And then, I think this project can make pot file with wp-cli like this

wp i18n make-pot . languages/quillforms.pot --ignore-domain

So generated quillforms.pot is contain of all translating text using __(), etc.

In the case of the gutenberg plugin, the text domain is not included when using the __() function inside of packages (like block package). Perhaps considering use outside of the WordPress context?

Please let me know if the above method is ok. I'm not sure because I don't have a good understanding of lerna.

I am currently not using the payment gateway package, but only

    "@quillforms/react-renderer-utils": "^5.4.0",
    "@quillforms/renderer-core": "^5.3.0",
    "@quillforms/types": "^3.0.14",

and I am noticing intermittent errors related to payment gateways.

I noticed @quillforms/payment-gateways exists in my node_modules folder as a dependency from @quillforms/renderer-core and the error message seems to be coming from here https://github.com/quillforms/quillforms/blob/master/packages/payment-gateways/src/api/index.ts#L37

Is there a way to avoid anything related to this module from being loaded?

Why are these payment modules being module unnecessarily?

Multiple choice block has 2 problems:
1- when the user hit the choice key via keyboard, the corresponding choice doesn't get selected.
2- When the user hit "tab", it doesn't jump to the next choice, it jumps to the next block.

Hello, big fan of the project. I have just one usecase I have not yet been able to figure out.

So I am creating a form where users can upload files, once the file is submitted I use the next() to go to the next form, however the percent completed does not update.

Is this something I can update manually?

./includes/class-shortcode.php

line: text-deocration: none;
should read: text-decoration: none;

thanks
andrew

Hi,

Quillforms is amazing but I've had an issue with the Quill Forms Entries Addon.

Once activated, it causes a fatal error in Matomo Plugin.
Spent 2 weeks with Matomo support, had to restore a backup of my website (lost all my quillfoms) and just found out that activating the Entries addon crashes Matomo again.

1. Is it possible to export the forms (or files) to prevent any loss ?

2. For your information, here is the error (related to Spyc)

Détails de l’erreur

Une erreur de type E_ERROR a été causée dans la ligne 101 du fichier /public_html/wp-content/plugins/matomo/app/plugins/Referrers/Social.php. Message d’erreur : Uncaught Error: Class "Spyc" not found in /public_html/wp-content/plugins/matomo/app/plugins/Referrers/Social.php:101
Stack trace:
#0 /public_html/wp-content/plugins/matomo/app/plugins/Referrers/Social.php(90): Piwik\Plugins\Referrers\Social->loadYmlData()
#1 /public_html/wp-content/plugins/matomo/app/plugins/Referrers/Social.php(58): Piwik\Plugins\Referrers\Social->loadLocalYmlData()
#2 /public_html/wp-content/plugins/matomo/app/plugins/Referrers/Social.php(43): Piwik\Plugins\Referrers\Social->loadDefinitions()
#3 /public_html/wp-content/plugins/matomo/app/plugins/Referrers/Social.php(133): Piwik\Plugins\Referrers\Social->getDefinitions()
#4 /public_html/wp-content/plugins/matomo/app/plugins/Referrers/API.php(482): Piwik\Plugins\Referrers\Social->isSocialUrl()
#5 [internal function]: Piwik\Plugins\Referrers\API->Piwik\Plugins\Referrers{closure}()
#6 /public_html/wp-content/plugins/matomo/app/core/DataTable/Filter/ColumnCallbackDeleteRow.php(74): call_user_func_array()
#7 /public_html/wp-content/plugins/matomo/app/core/DataTable.php(532): Piwik\DataTable\Filter\ColumnCallbackDeleteRow->filter()
#8 /public_html/wp-content/plugins/matomo/app/plugins/Referrers/API.php(483): Piwik\DataTable->filter()
#9 /public_html/wp-content/plugins/matomo/app/plugins/Referrers/API.php(433): Piwik\Plugins\Referrers\API->filterWebsitesForSocials()
#10 /public_html/wp-content/plugins/matomo/app/plugins/Referrers/API.php(459): Piwik\Plugins\Referrers\API->Piwik\Plugins\Referrers{closure}()
#11 /public_html/wp-content/plugins/matomo/app/plugins/Referrers/API.php(436): Piwik\Plugins\Referrers\API->combineDataTables()
#12 /public_html/wp-content/plugins/matomo/app/plugins/Referrers/API.php(421): Piwik\Plugins\Referrers\API->completeSocialTablesWithOldReports()
#13 [internal function]: Piwik\Plugins\Referrers\API->getSocials()
#14 /public_html/wp-content/plugins/matomo/app/core/API/Proxy.php(244): call_user_func_array()
#15 /public_html/wp-content/plugins/matomo/app/core/Context.php(28): Piwik\API\Proxy->Piwik\API{closure}()
#16 /public_html/wp-content/plugins/matomo/app/core/API/Proxy.php(335): Piwik\Context::executeWithQueryParameters()
#17 /public_html/wp-content/plugins/matomo/app/core/API/Request.php(267): Piwik\API\Proxy->call()
#18 /public_html/wp-content/plugins/matomo/app/plugins/API/ProcessedReport.php(377): Piwik\API\Request->process()
#19 /public_html/wp-content/plugins/matomo/app/plugins/API/API.php(283): Piwik\Plugins\API\ProcessedReport->getProcessedReport()
#20 [internal function]: Piwik\Plugins\API\API->getProcessedReport()
#21 /public_html/wp-content/plugins/matomo/app/core/API/Proxy.php(244): call_user_func_array()
#22 /public_html/wp-content/plugins/matomo/app/core/Context.php(28): Piwik\API\Proxy->Piwik\API{closure}()
#23 /public_html/wp-content/plugins/matomo/app/core/API/Proxy.php(335): Piwik\Context::executeWithQueryParameters()
#24 /public_html/wp-content/plugins/matomo/app/core/API/Request.php(267): Piwik\API\Proxy->call()
#25 /public_html/wp-content/plugins/matomo/app/core/API/Request.php(560): Piwik\API\Request->process()
#26 /public_html/wp-content/plugins/matomo/classes/WpMatomo/Report/Data.php(54): Piwik\API\Request::processRequest()
#27 /public_html/wp-content/plugins/matomo/classes/WpMatomo/Report/Renderer.php(100): WpMatomo\Report\Data->fetch_report()
#28 /public_html/wp-includes/shortcodes.php(355): WpMatomo\Report\Renderer->show_report()
#29 [internal function]: do_shortcode_tag()
#30 /public_html/wp-includes/shortcodes.php(227): preg_replace_callback()
#31 /public_html/wp-content/plugins/matomo/classes/WpMatomo/Admin/views/summary.php(154): do_shortcode()
#32 /public_html/wp-content/plugins/matomo/classes/WpMatomo/Admin/Summary.php(118): include('/...')
#33 /public_html/wp-includes/class-wp-hook.php(308): WpMatomo\Admin\Summary->show()
#34 /public_html/wp-includes/class-wp-hook.php(332): WP_Hook->apply_filters()
#35 /public_html/wp-includes/plugin.php(517): WP_Hook->do_action()
#36 /public_html/wp-admin/admin.php(259): do_action()
#37 {main}
thrown

We are using quillforms and we reached a deadend where our forms should be accessible to my authenticated users only is it possible to add it as a feature ?

Describe the bug

I followed the getting started guide and added it to a new react app using vite.

When I want to compile it, I get the following error:

    node_modules/@quillforms/utils/build-module/normalize-icon-object.js:8:31:
      8 │ import { default as tinycolor, mostReadable } from 'tinycolor2';
        ╵                                ~~~~~~~~~~~~

/Users/andrashee/code/public/survey/node_modules/esbuild/lib/main.js:1575
  let error = new Error(`${text}${summary}`);
              ^

Error: Build failed with 1 error:
node_modules/@quillforms/utils/build-module/normalize-icon-object.js:8:31: ERROR: No matching export in "node_modules/tinycolor2/esm/tinycolor.js" for import "mostReadable"

I tried to fix the tinycolor2 dependency to the same version as you use in the @quillforms/renderer-core package.
Any ideas?

Here my package.json

{
	"name": "survey",
	"private": true,
	"version": "0.0.0",
	"scripts": {
		"dev": "vite",
		"serve": "$npm_execpath run dev",
		"build": "tsc && vite build",
		"preview": "vite preview"
	},
	"dependencies": {
		"@quillforms/react-renderer-utils": "^3.0.1",
		"@quillforms/renderer-core": "^3.0.1",
		"react": "^18.2.0",
		"react-dom": "^18.2.0",
		"tinycolor2": "^1.4.2"
	},
	"devDependencies": {
		"@types/react": "^18.0.21",
		"@types/react-dom": "^18.0.6",
		"@vitejs/plugin-react": "^2.1.0",
		"typescript": "^4.6.4",
		"vite": "^3.1.0"
	}
}

Thanks!

Describe the bug
A clear and concise description of what the bug is.

Missing types in react-renderer-utils. blocks could use a DisplayProps.

To Reproduce
npm install --save @quillforms/react-renderer-utils
Notice that there are no types there.

registerBlockType("name", {..., display: ({id,
next,
attributes,
setIsValid,
setIsAnswered,
setValidationErr,
showNextBtn,
blockWithError,
val,
setVal,
showErrMsg,}: any) => {})

Expected behavior
A clear and concise description of what you expected to happen.

Screenshots
npm install --save @quillforms/react-renderer-utils
There are types there.

registerBlockType("name", {..., display: ({id,
next,
attributes,
setIsValid,
setIsAnswered,
setValidationErr,
showNextBtn,
blockWithError,
val,
setVal,
showErrMsg,}: DisplayProps) => {})

Describe the bug
Module '"@quillforms/renderer-core"' has no exported member 'useCurrentBlock'.ts(2305)

To Reproduce
import { useCurrentBlock } from "@quillforms/renderer-core";
const currentBlock = useCurrentBlock();

Expected behavior
to import useCurrentBlock successfully

Desktop (please complete the following information):

• OS: arch linux
• Browser: firefox
• Version: 113.0.2

Where I think its the bug

https://github.com/quillforms/quillforms/blob/master/packages/renderer-core/src/hooks/index.ts

I think the error its that useCurrentBlock its not exported

Describe the bug
Absolutely love the project. Thanks so much.

One small bug — if a required answer is left blank, when the user clicks the submit button they are sent back to the unfilled field. When they fill in the required field they should be sent back to the submit button. Instead, they’re sent to the next (completed) question and then have to scroll through all their answers again to get to the submit page. This is OK if the form is only a few questions long but if you have 40+ question it takes a long time for the user to scroll through.

To Reproduce
Steps to reproduce the behavior:

1. Fill out a form but leave one required field blank
2. Press the submit button
3. You'll be scrolled back to the required field
4. Fill in the required field, and click OK
5. Instead of being scrolled back to the submit button, you'll be sent to the next (filled) question

Expected behavior
The user should be scrolled back to the submit button once they've filled in a missing required field

Desktop (please complete the following information):
All browers

Smartphone (please complete the following information):
All browers

Additional context
You can see the issue on https://quillforms.com/quillforms/support-form/ though it's not as annoying as the form isn't really long

Currently, the user can close the builder tab or navigates to another page although there is still unsaved changes in the builder.

I can not create a new jump logic rule.

Required fields currently don't have any indication for being required.

Describe the bug
I am trying to install and run the quillforms on my local machine, but I can't

To Reproduce
Steps to reproduce the behavior:

1. Run npm i or Run npm ci

Expected behavior
Install all the dependencies and run the project

Describe the bug
When trying to run a wp command on CLI, the following error is thrown

Undefined constant 'QuillForms_Entries\Vendor\FALSE' in /home/DIR/wp-content/plugins/quillforms-entries/dependencies/build/vendor/mustangostang/spyc/Spyc.php:1251

Which leads to the following piece of code:

if (empty($_SERVER['PHP_SELF']) || \QuillForms_Entries\Vendor\FALSE === \strpos($_SERVER['PHP_SELF'], 'Spyc.php')) {
    break;
}

To Reproduce
Steps to reproduce the behavior:

1. Go to the WP root folder
2. Run any WP command, like wp option get siteurl
3. See error

Expected behavior
No errors thrown.

Plugin info:

• QuillForms 2.1.0
• customthankyouscreenblock - 1.6.0
• entries - 3.0.0
• facebookpixel - 1.1.0
• googleanalytics - 1.1.0
• googlesheets - 1.5.0
• logic - 2.0.0
• opinionscaleblock - 1.2.0
• phoneblock - 1.2.1
• picturechoiceblock - 1.4.1
• ratingblock - 1.2.0
• signatureblock - 1.0.0
• webhooks - 1.0.1

Server info:

• Ubuntu 20.04
• PHP 7.4.33
• WordPress 6.1.1

Describe the bug
A clear and concise description of what the bug is.

To Reproduce
Steps to reproduce the behavior:

1. Go to this line
   
2. See error

Expected behavior
I think It must be deleted.

Screenshots
N/A

Desktop (please complete the following information):
N/A

Smartphone (please complete the following information):
N/A

Additional context
N/A

How can I change the background color of the dropdown to another color on mobile. By default it is white but I wanted to put it in black and I don't find any option, not even by CSS rule does the plugin accept it.

Cannot read properties of undefined (reading 'quotationMarks')
TypeError: Cannot read properties of undefined (reading 'quotationMarks')
at CounterIconComponent (http://localhost:3001/static/js/bundle.js:54348:35)
at renderWithHooks (http://localhost:3001/static/js/bundle.js:134559:22)
at mountIndeterminateComponent (http://localhost:3001/static/js/bundle.js:137845:17)
at beginWork (http://localhost:3001/static/js/bundle.js:139141:20)
at HTMLUnknownElement.callCallback (http://localhost:3001/static/js/bundle.js:124151:18)
at Object.invokeGuardedCallbackDev (http://localhost:3001/static/js/bundle.js:124195:20)
at invokeGuardedCallback (http://localhost:3001/static/js/bundle.js:124252:35)
at beginWork$1 (http://localhost:3001/static/js/bundle.js:144126:11)
at performUnitOfWork (http://localhost:3001/static/js/bundle.js:143373:16)
at workLoopSync (http://localhost:3001/static/js/bundle.js:143296:9)

I'm using the Quill Forms embed on my website (not Wordpress), and I want to restrict the responses to only come from my domain.
Is there a way to do that? I basically don't want the form to open elsewhere except on my website.

Typeform support images and open text field (other) in multiple-choice blocks.
After looking at the implementation it should be relatively easy to add.

Happy to contribute to the project to avoid having to fork or create a custom block just for that.

LMK if I can help or if this is on the road map at all.

Thanks.

Dynamic data
" formObj={{ blocks: state, ...}} "

on setState the data is not rendering on form.

///////////////

put blocks data in a state and update the state
the updated state value is not rendering in the form.

Of course, storybook is on the plan and it is urgently needed as the project goes popular.

Pretty urgent!

Describe the bug
When using the package in a NextJS project, it complains that a Global CSS cannot be imported from within node_modules.

To Reproduce

1. Start a fresh NextJS Project
2. Install the library
3. Import the library
4. See error

Expected behavior
Here is a explanation from NextJS in how to fix it: https://nextjs.org/docs/messages/css-npm

Screenshots

Desktop (please complete the following information):

• OS: iOS
• Browser: Chrome

The app doesn't support translations yet and this is crucial part at the app.

Is there a way to close a form and display a message that the form is close?

There is an issue now in the prefix we use in our functions, constants and classes that the prefix (qf_) is so generic and can cause conflicts easily.
Better way to handle this is to have namespaces for classes and all functions and constants to be prefixed with "quillforms_" instead of "qf_"

I want to justify left on questions, answers, and the button. I also want bold type. Please help me with the CSS. Thank you!!!

http://calvinbecerra.xyz/quillforms/contact/

Hi,

Can it be used with react 18 projects?

I tried and got the error:

Error
Invalid hook call. Hooks can only be called inside of the body of a function component.

You can check my codesandbox fork here: https://codesandbox.io/s/quill-forms-example-typeform-clone-in-react-js-and-typescript-forked-301lcb

Hi, i am GA/GTM expert, and a customer asked me to track funnel of a form made with quillform.

I usually use Google Tag Manager, but your product don't seems to give anything to track steps with it.
Is there a way to generate a datalayer event for each step?

For now i used the GA integration, but it seems we can connect only one property, my customer have GA-UA and GA4.
How to connect both to the plugin?

And last question, we need to track the form sent to confirme conversion with google ads, but with no datalayer event and no thank you page GTM can't know when conversion is confirmed.
How to set up a redirection to a thank-you page automatically?

Thank you.

In the theme editor, when I hover over the circular color picker's options, the popover tooltip seems to have some unexpected positioning.

In Firefox (version 89.0.1), the tooltips show up beneath the circular options. It's not very noticeable on the bottom row of colors, but it is for colors on the top row:

I experimented with modifying the z-index value for various elements in this tree, but I couldn't get the tooltip to show up at the right level. 🤔

I thought this might be a rendering issue with Firefox, so I loaded things up in Chrome (version 91.0.4472.114) to see how they looked, and the tooltips are showing up further down the page:

Hi All, is there any plans to adapt this for a React Native implementation?