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.

Widget Form display problems on different screen resoultion(s)?

  1. I have recently ran into this problem with a widget form. Up until last night the widget form looked great on FireFox, IE and Chrome - on all screen resolutions. Now, a few of the fields are misaligned - only on IE (see picture). Here is the thing though on my laptop (res. of 1366x768) is looks fine, how it should be.

    <img src="http://simplequotelifeinsurance.com/CC/GravityHelp.png"/>

    I am only seeing this problem on my desktop (res. of 1920x1080) - using IE.

    Any help/advice would be great.

    Posted 13 years ago on Saturday May 7, 2011 | Permalink
  2. I think I have narrowed it down to that I am having problems with breaking the fields into thirds.

    Noticed I have the same problem on a page where I have another form.

    http://simplequotelifeinsurance.com/CC/FormProblems.png

    Posted 13 years ago on Saturday May 7, 2011 | Permalink
  3. You will need to define a height on the containing list items for IE then so you don't get the odd hanging effect from the floated elements. Some of the elements have sub-labels and others don't so the height discrepancy is causing the problem.

    Posted 13 years ago on Saturday May 7, 2011 | Permalink
  4. Thanks for the response, but where would I make the changes?

    Posted 13 years ago on Sunday May 8, 2011 | Permalink
  5. You would define the CSS in your themes stylesheet. That is where all custom CSS would be placed for targeting and styling form elements using CSS.

    Posted 13 years ago on Monday May 9, 2011 | Permalink
  6. Could you give and example of the code please.

    Posted 13 years ago on Monday May 9, 2011 | Permalink
  7. Problem resolved...thanks for all the help guys!

    Posted 13 years ago on Monday May 9, 2011 | Permalink

This topic has been resolved and has been closed to new replies.