PLEASE NOTE: These forums are no longer utilized and are provided as an archive for informational purposes only. All support issues will be handled via email using our support ticket system. For more detailed information on this change, please see this blog post.

Problems with long multi-form in IE8

  1. mbone
    Member

    Hello,

    I am seeing some issues with a long multi-page form (6 pages) in IE8. The form looks pretty much as I expected in FF, but in IE8 I am seeing weirdness.

    http://bestmortgageloans.ca/beta/applyonline/

    - The biggest thing I notice is the right and bottom scroll bars (that seem to scroll the text, but not the form elements)
    - I am also noticing some places where the gf_****_third classes were used are not lining up (second line on form)

    This is with the 1.5 Beta 3
    Thanks for any help you can provide.

    Posted 14 years ago on Saturday November 27, 2010 | Permalink
  2. This is the deal, the "ready styles" are simply pre-built helper styles but are still just CSS rules and aren't bulletproof by any means. They use floats, and clears to achieve the column layouts. How you arrange the fields and even the types/sizes of the fields make a difference in the final results. Inheritance from your theme CSS may also cause problems.

    You're mixing different types of fields - some with sub-labels, others with descriptions, etc with others that don't have any sub-text or sub-labels. This means the adjacent fields are different heights and when the elements on the next line float, they "hang" on the different sized elements above. example: http://grab.by/7BSy

    What you need to do to remedy this, is define equal heights for elements in each row if you don't want this behavior. Since you're only seeing this in IE, you can try just adding the height rules, etc. in an IE conditional block.

    <!--[if IE]>
    
    <style type="text/css">
    body .gform_wrapper .top_label li.gfield.gf_left_half,
    body .gform_wrapper .top_label li.gfield.gf_right_half {margin:0 0 8px 0!important; height:80px;}
    
    body .gform_wrapper .top_label li.gfield.gf_left_third,
    body .gform_wrapper .top_label li.gfield.gf_middle_third,
    body .gform_wrapper .top_label li.gfield.gf_right_third {height:80px;}
    
    body .gform_wrapper ul.gform_fields {overflow:inherit}
    
    </style>
    
    <![endif]-->

    Honestly, even with the heights defined, your form layout looks pretty random with the fields in different column formats everywhere. It might be better to stick with just a 2 column layout all the way around. I understand you're trying to conserve space, but as a user, I would find this more confusing than helpful.

    I'm going to experiment with the CSS - a couple of other ideas to see if I can forego some of this issue in the final 1.5 release.

    Posted 14 years ago on Sunday November 28, 2010 | Permalink
  3. mbone
    Member

    Hi Kevin,
    Thank you for the very fast response. Your solution cleared up most of the visual differences in IE.

    I agree with what you said about the randomness, but once I tighten up the surrounding div (ie not full page width) I think it looks much better. This plug-in is amazing.

    I have noticed two issues with the multi-page form though:

    1) I gave all 6 of my pages names [in the 'start paging' properties] and saved the form. The page names showed up fine. When I viewed the form a few hours later though, the names had cleared themselves out of the properties. This has happened a few times for me.

    2) The 'Previous' button does not go to the previous page. It is taking the form to the next page (or submiting the form if on the last page)
    This is happening in IE and FF and it is happening in the form URL above. I am using images for the next/previous/submit buttons. Not sure if that makes a difference.

    Thanks for the help so far.
    Great product!

    Posted 14 years ago on Monday November 29, 2010 | Permalink
  4. Okay, thanks for the report, we'll look into into those issues.

    Posted 14 years ago on Monday November 29, 2010 | Permalink
  5. @mbone,
    I was able to recreate your issue with the "Previous" button. It is a bug related to the image buttons. I will work on getting it fixed for the next release.

    As far as the page names disappearing, we have had reports of that, but were never able to replicate it. Is this something you can replicate, or does it happen completely at random? Does it happen without you even going to any of the Gravity Forms admin pages?

    Thanks for your help!

    Posted 14 years ago on Monday November 29, 2010 | Permalink
  6. mbone
    Member

    Thank you for looking into these issues so quickly.

    I can not replicate the issue, although I am checking the page names property after every action I perform. Hopefully I can help track down a certain action that might be causing this.
    As far as I can tell so far, I have been in the gravity form admin pages when it happens. The page names remain when I have not gone in the admin.

    Posted 14 years ago on Monday November 29, 2010 | Permalink
  7. I was finally able to figure out what was going on. The page names weren't being initialized properly unless you expanded the "Start Paging" properties. If you saved the form without looking at the page names, they were getting cleared out.

    I have a new version with your two issues resolved. If you want to take it for a spin, email me at alex@rocketgenius.com and I will send it to you.

    Posted 14 years ago on Monday November 29, 2010 | Permalink
  8. mbone
    Member

    Hi Alex,

    Thanks for sending me that new version of the Beta. Both of those issues I was having are gone.

    I did notice an issue with the date field in the version you sent though (IE and FF) Where it had pieces of the calendar all over the place. You won't be able to see it in my link above though, because I replaced the forms.css with the one from the original 1.5b3 (this fixed the issue)

    Just wanted to let you know.

    Thanks again.
    M.

    Posted 14 years ago on Tuesday November 30, 2010 | Permalink