I would be fine leaving a buffer in the height, but I'm worried my users, the ones who would be writing and using the surveys, would not be comfortable/capable with playing with the parameters.

Wufoo's Support team says this is not something set by CSS, but rather the scroll bar is a parameter in the iFrame call. Is it possible to add a parameter to the widget macro that passes 'scrolling="yes"' to the iFrame? (Let me know if this would be better suited as a feature request)

I tried using Wufoo's iFrame embed code with Adaptavist's iFrame macro, but by design, Adaptavist has disabled parameters like that.

This is the same issue, but it's not possible to fix.

The way it currently works with Wufoo is if you don't specify a height, it uses a default height of 500 pixels regardless of how long the form really is. The fact that it looks good on your form is unfortunately just a coincidence. The error message of course makes it longer, causing it to overflow. Normally it would create a scrollbar but due to some CSS code on Wufoo's end which is not in our control, it doesn't. Confluence also can't detect the height to due limitations imposed by browsers for security reasons. Your best bet would be to specify a height long enough for the errors.

I'm not sure if this qualifies for a separate issue (let me know and I can create one), but while IE and FF render the Wufoo form correctly when you leave the height tag off, if you get an error response back (forgot to fill in a required field, etc), it adds a new element to the form, and pushes the submit button out of view.

So, to repro:
-Import a wufoo form with a required field (looks good here)
-Submit this form without that required field

Is there any way to watch for return data and update the height attribute then?

This has been implemented, although the fix does not apply to Wufoo (cannot be fixed). At present the fix only applies to DabbleDB.

Also, this couldn't be done in time for 3.3, so it'll most likely end up in 3.3.1 or 3.4

This issue is a duplicate of https://studio.plugins.atlassian.com/browse/WC-10

I spoke to Sherif about this today. He said it wouldn't make sense to try to automatically detect the height of the page because in this case the height is actually being set by the user (notice height=800px in the wiki code).

Instead, we should be adding scroll bars where the page is longer than the height specified (i.e. set scrolling="auto" on the iframe). However, as I mentioned before, this will not fix the Wufoo page as it has CSS code that hides the scrollbar. But it might fix embedding other pages that are too long.

I'm afraid this can't be fixed, and the best way that I know to workaround it would be to specify an appropriate height to the macro.

Reason:
To fix this, we would need to get a hold of the document object in the iframe and calculate its height. Unfortunately, the document object in the iframe belongs to another domain and the JS in Confluence is not permitted to access it.

http://www.webdeveloper.com/forum/showthread.php?t=189515