- pandcproductionsAsked on September 26, 2012 at 10:52 PM
All of a sudden your iframe tool is BROKE!!! It defaults to scrolling "yes" height"100%" BUT it is not 100%.
This is a NEW problem. Earlier today I got this code from one of my forms-
height:12344px</span>; border:none;" <span style="background-color:#888888;" _mce_style="background-color: #888888;">scrolling="no"</span>></p> <p>
JUST NOW I got this code FROM THE SAME JOTFORM!!!-
height:100%</span>; border:none;" <span style="background-color:#888888;" _mce_style="background-color: #888888;">scrolling="yes"</span>></p> <p>
I have tried every possible solution. This is the situation on all of my forms and if I create a new form it does the same thing.
This is a problem because I have 4 forms that are on all of my websites and I am constantly adding to new sites. I need this resolved immediately. Sorry to sound like an A hole but we pay for jotform and I need it to work for my business to work.
- JotForm SupportidarktechAnswered on September 26, 2012 at 11:03 PM
May we know the website URL where you've embedded your forms? We'll add it to our reports and addressed it to our development team so we can compare both codes and analyze the disadvantages of the new iframe code.
We'll await your reply.
P.S. I have made this thread private so you can share your website URL here. Thanks.
- pandcproductionsAnswered on September 26, 2012 at 11:25 PM
First, Please make this post public so other people can add to the conversation.
I appreciate your prompt response. However, I am not going to use the new iframe code because it is absolutely stupid. So I can't give you a URL that I am using it in. Just copy and paste both into any website and you will see the problem. It is 11:15 PM in Ohio and I am now going through all of my sites and manually fixing all of the damage that Jotform has done today. I don't know what authority you have when it comes to billing, but to compensate me for all the extra work I've had to do I figure I should get the next 2.5 years of service for free. I use jotform because it is quick and easy. This situation is the antithesis of quick and easy.
- JotForm SupportidarktechAnswered on September 26, 2012 at 11:43 PM
Done. Thread is now public.
Actually this the first report about the new format of iframe embed code and we appreciate your feedback about this. First, I can't figure out what you mean on "it is not 100%" since I can't replicate the problem when I've embedded the iframe code with 100% height (this is actually good for mobile views). However, I know there might be some circumstances that height 100% property might be a problem so I have now raised this issue to our development to go with the further investigation.
Also, I don't think you have to update your previous iframe embed codes because that wont be affected. This is only for "new" generated iframe embed codes.
Thanks for your feedback. We'll get back to you once we heard form our developers about this.
- pandcproductionsAnswered on September 27, 2012 at 12:16 AM
I am under the impression that "100%" means that the iframe adjusts itself to show the entire form. It is NOT doing this function. If it were it would be perfect. If I am mistaken about that property of an iframe, please let me know.
On my end, when I view the iframe, I can only see a small cutout of the form with a very long scroll bar. I am manually changing "100%" to "12000 px". This is the only way I can display the entire form.
Furthermore, I would just use the embed code, but that has been F'd for a long time now due to an issue on Jotforms end. I know this based on other users posting this issue and responses by support. The only reason I am using an iframe is because that was the recommended solution to your embed issues.
- pandcproductionsAnswered on September 27, 2012 at 12:22 AM
I understand how this can be helpful in mobile format. By simply adding options to the embed menu (like youtube) to help users solve their individual needs(the way you have a "secure" checkbox that alters the code) you would be able to avoid these issues.
I envision options like:
scroll: O Yes O No O Auto
- jeanettebmzAnswered on September 27, 2012 at 12:23 AM
And you are correct 100% means it will adjust in most cases.However, changing scroll to YES, might sort most of the problems. Your suggestion might be taken into consideration.
- JotForm FounderaytekinAnswered on September 27, 2012 at 05:08 AM
Can we see the problem? Can you post the URL of the page where you have this problem?
- pandcproductionsAnswered on September 27, 2012 at 07:33 PM
Here is a Url that I have used the old AND New code on. 2 things I want to mention.
1. I understand what jeanettebmz is saying. I guess I just don't understand why 100% doesn't mean "100%" in every situation.
2. Please notice that the form collapse tool is no longer bringing the screen to the top of the open form collapse. This was a great feature. Did you remove it or is something wrong?
- JotForm SupportjonathanAnswered on September 27, 2012 at 08:03 PM
Thank you for accomodating and providing the information requested.
As mentioned already, this iframe issue already have a ticket and our dev team are currently looking into it.
We all know that the generated iframe embed code was changed from how it was previously. Specifically on the 'height' parameter value.
Previously, the iframe code provided was usually a dynamic value (in pixel) of the current form height. But now it is fixed to percentage value(as in 100%), presumably of the form's height. This change maybe was done to address in-mobile views, and it actually work. As said already, there are rare case when it did not work (such as yours).
For the meantime, as you had figured out already-- setting the iframe code to 'fix' height value(according to form's height) will retain how it worked as before.
I simulated this using Chrome's tool on the test site you provided. I used 440px as the 'fix' height value, and it seems to work fine.
You will be updated when new information are available.
Thank you for your patience and understanding.
- JotForm SupportozanAnswered on September 28, 2012 at 04:54 AM
This was a fix for facebook iframes, but unfortunately other types of iframes are effected too, sorry for the inconvenience. So we seperated the source for facebook and stand alone iframes, since they were the same beforehands. I hope this fixes your problem.