- RonjaAsked on March 22, 2017 at 05:59 AM
with every template i clone or form that i built from the scratch there is a massive background created around the actual form.
when embedding the form on a webiste that uses a footer area, there is massive white space below the form and before the footer.
how can I adjust / delete this free space?
You can see the issue at the form URL:
The form itself (yellow form background) has the correct size, but there is a scroll bar at the right side indicating the "size" of the background which results in white space below the form in wordpress.com.
Do you have any idea how to solve this?
- JotForm SupportKiranAnswered on March 22, 2017 at 11:57 AM
I understand that the height of the form is being displayed larger than the screen. Please try injecting the following CSS code to the form so that the form height should be adjusted.
height: auto !important;
If the issue still persists, please provide us with the web page URL where the form is embedded so that we can take a look and provide you with necessary assistance.
- RonjaAnswered on March 23, 2017 at 03:29 PM
thanks for your answer. However this is not solving the issue.
You can take a look here: https://ronjahartmann.wordpress.com/zusammenarbeiten/formular-test/
this is a test page, where I just inserted the form so you see, what I am referring to.
Ultimately, I want to have the form background and the background (page background?) in the same color, but for visualizing the issue I changed it to two different colors..
The size of the form background (yellow) is fine, but there is this grey area which is called "page" probably (I am using the German version of the web app)
This greyish area is too long. Is there a way to adjust/shorten this area?
- JotForm SupportKiranAnswered on March 23, 2017 at 04:52 PM
Okay. I see that the height of the form is displaying with more empty space than the form. As I investigate the issue further, the [embed] tag in the WordPress is resizing the iframe width to a fixed width of 1000px which is causing the issue.
Let me forward the issue to our backend to investigate the issue further. Once we have any update in this regard, you'll be posted here.
- RonjaAnswered on March 24, 2017 at 04:04 PM
Thank you, Kiran!