No waitlist anymore. ![]()
Just select βFormβ when creating a new app in your workspace.
As always, we truly love hearing your feedback.
To keep things organized and moving fast, please post your feedback here:
Feature requests
Issues & bugs
No waitlist anymore. ![]()
Just select βFormβ when creating a new app in your workspace.
As always, we truly love hearing your feedback.
To keep things organized and moving fast, please post your feedback here:
Feature requests
Issues & bugs
Amazing! Almost there!
Numbers next? Iβm guessing a form where someone is able to put in number-hours, number-money, number-quantity is quite useful. I canβt move to Tape before the feature is there β‘Μ How far away are we? All the best!
Hi @MitzaBarnes,
great to hear that this is the last missing piece for you to make the move over to Tape, thatβs amazing news ![]()
Weβre almost there: itβs a matter of days, not weeks. Weβre planning to roll out the number field next week.
Looking forward to having you on board! ![]()
Best,
Leo
Fantastic!!! That is honestly fantastic!
Hello, Iβm running into an issue with the iframe height:
On the other hand:
What Iβm trying to achieve:
I would like the iframe to automatically resize based on its content height, so that:
Question:
Does Tape support automatic iframe resizing (e.g., via postMessage or a built-in embed script)?
If not, is there any recommended way to make the embedded form responsive in height? If not, I want you to suggest this as item to roadmap. Then I will be able to replace WPForms with Tape Forms and this will be perfect. ![]()
Thanks, VladimΓr.
The postMessage API exists specifically to work around this. The iframe sends its height to the parent page, the parent page listens and resizes the iframe accordingly.
Unfortunately, Tape forms donβt have this set up currently, so the only option that you have on your end is making the formβs height bigger than the anticipated information inside of it.
Thank you. I know that I can do this, but this looks poor too, when form is initially short. But maybe in future it will get some improvement.
Hi @Samuel222,
thanks a lot for your detailed report, this is incredibly helpful for us to fully understand your use case and the current limitation. We really appreciate the effort you put into describing it so clearly. ![]()
We will take a closer look at this topic, including whether and how we could implement automatic iframe resizing, what the development effort would be. We will keep you updated as soon as we have more clarity.
Also, a big thanks to @1F2NS for the helpful explanation, much appreciated!
And thank you again, Samuel, for raising this feature request. We will review it carefully and get back to you soon.
Best,
Leo
Hi @Leo, thank you for your reply.
Also I want to give you next tip for enhancement - it will be great to have possibility to set if form can be submitted by pressing Enter or not. Now when you press Enter, form is submitted, but visitor can press Enter by mistake. Safer option for some Tape managers may be to force a click on the Submit button.
Thank you.
Regarding the form - are there any ideas so far to protect public forms from spam submissions? Whenever there are public forms, some day bots will show up and hammer your form with spam.
In the past we used approaches like:
Long term - and depending on type of the form - only variant 3 will substantially work. Given the many different providers, probably some custom code field could work.
Is there anything server side, that prevents bots? As its an iframe you control the server. Something like only x submissions from the same IP within timeframe y already is a great method to stop spam (spammers donβt have time to wait).
(more background also in the Forum post: Be careful with public forms // danger of backscatter spam)
To be clear - I havenβt experienced it in Tape yet. But I want to help prevent it to happen ![]()
Update:
phone field ![]()
Update:
email field ![]()
Update:
link field ![]()
The only remaining field is now the Checklist field. Once that is released, the new record experience will officially support all Tape field types, which will be another major milestone for us
![]()