Update: 🆕 File field for forms
Cool!
Some ideas for further enhancing webforms:
- hidden field for JavaScript to read e.g. referring URL or read a variable from the URL (e.g. to use one application form for a variety of job posts, but to automatically identifying the referring one),
- allow to change the wording of the submit button, (e.g. apply, order etc.)
(I bet other field types like email and phone will follow anyway
).
@Leo since I have the ‘New Record’ I can’t create new Forms anymore - the option to do so is gone. Could you reactivate that plesase.
Hi @Kollaborateur,
thanks a lot for the report! It might indeed be an issue with the feature flags. We should definitely double-check that for all users to be safe.
Could you please send me the email address of the user where this happens via Direct Message here in the Community, so we can make sure we’re checking the correct account?
Thanks again and have a great day!
Leo
Update: Single-select, multi-select, and status fields can now be displayed as dropdowns.
Any ETA on redirect after submission? That one missing feature is still causing us to need a different form solution for several use cases
thanks a lot for reaching out ![]()
At the moment, our full focus is on developing the relation field, including all connected features, which is a pretty big and important building block for us. Once that is done, we’ll take another look at the roadmap and see when a redirect after submission could fit in.
However, we’ll also do a quick check on the effort required and see if there’s any chance to squeeze it in earlier. I’ll definitely keep you posted if we see an opportunity for a sooner release.
Best,
Leo
It’s been years, and I’ve said it multiple times, but it’s still so refreshing to work with a partner as transparent and honest as you and the rest of the Tape team.
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:
- If I set a fixed height (e.g., 600px), the form initially displays correctly.
- However, when the form expands (e.g., longer text input, conditional fields, validation messages), the iframe height does not adjust dynamically.
- As a result, an internal scrollbar appears inside the iframe, which creates a poor user experience.
On the other hand:
- If I set the height to 100%, the iframe renders as a very small strip (because the parent container has no explicit height), making it unusable.
What I’m trying to achieve:
I would like the iframe to automatically resize based on its content height, so that:
- the iframe grows/shrinks dynamically,
- no internal scrollbar appears,
- and the page itself scrolls naturally instead.
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