https://legacy.forums.gravityhelp.com/topic/16rc1-formatting-bug Gravity Support Forums Topic: 1.6rc1 formatting bug en-US Sat, 04 Apr 2026 18:17:36 +0000 http://bbpress.org/?v=1.0.1 q https://legacy.forums.gravityhelp.com/search.php https://legacy.forums.gravityhelp.com/topic/16rc1-formatting-bug#post-36299 Tue, 27 Sep 2011 01:00:10 +0000 Kevin Flahaut 36299@https://legacy.forums.gravityhelp.com/ <p>I'm happy I could help out. The float on the wrapper was allowing the following elements to float into what little space there was left to the right of the form wrapper.</p> <p>I did notice that the majority of the HTML errors were related to the quote rotator script you have. It looks like it's defining the same element ID over and over so once you tidy that up, you're probably about 85% of the way there with that piece.</p> <p>Good luck with that and as always, let us know if you need anything else. </p> https://legacy.forums.gravityhelp.com/topic/16rc1-formatting-bug#post-36298 Tue, 27 Sep 2011 00:56:29 +0000 muhromatic 36298@https://legacy.forums.gravityhelp.com/ <p>Kevin:</p> <p>Thank you Sir... I just found out that an intern put that css there to try to justify the form to the left.</p> <p>I fixed it and adjusted the form myself. As for the html errors... looks like I have some work to do.</p> <p>Thanks as always... you guys are the best.</p> <p>GM </p> https://legacy.forums.gravityhelp.com/topic/16rc1-formatting-bug#post-36295 Tue, 27 Sep 2011 00:23:29 +0000 Kevin Flahaut 36295@https://legacy.forums.gravityhelp.com/ <p>Conclusion: Not A Bug</p> <p>Your issue is happening because a float property that has been added to your forms.css file that doesn't belong there. There shouldn't be a "float:left" property on the .gform_wrapper class</p> <p>Your CSS: <a href="http://bit.ly/paofnF" rel="nofollow">http://bit.ly/paofnF</a></p> <p>The default forms.css file that's packaged with the 1.6 release candidate doesn't have this so it must have been added on your end.</p> <p>Default CSS: <a href="http://bit.ly/rtxJEE" rel="nofollow">http://bit.ly/rtxJEE</a></p> <p>If you remove the float property from your forms.css file, then you'll see that your issue goes away. This wasn't an issue with this release, but an issue caused by a customization.</p> <p>screenshot ( float disabled ): <a href="http://bit.ly/pAzIFs" rel="nofollow">http://bit.ly/pAzIFs</a></p> <p>Your page is also full of HTML errors which could cause potential display problems. You might want to <a href="http://validator.w3.org/check?uri=http%3A%2F%2Fwww.cfcbd.com%2Fsupport&amp;charset=%28detect+automatically%29&amp;doctype=Inline&amp;group=0" rel="nofollow">check the HTML validator</a> to help you identify and correct these problems. </p> https://legacy.forums.gravityhelp.com/topic/16rc1-formatting-bug#post-36292 Mon, 26 Sep 2011 23:32:40 +0000 Kevin Flahaut 36292@https://legacy.forums.gravityhelp.com/ <p>Okay, Thanks. I'll check it out as soon as I can and let you know what I find. </p> https://legacy.forums.gravityhelp.com/topic/16rc1-formatting-bug#post-36289 Mon, 26 Sep 2011 22:32:20 +0000 muhromatic 36289@https://legacy.forums.gravityhelp.com/ <p>Kevin:</p> <p>Thanks, I sent a link via priority support.</p> <p>GM </p> https://legacy.forums.gravityhelp.com/topic/16rc1-formatting-bug#post-36287 Mon, 26 Sep 2011 21:44:14 +0000 Kevin Flahaut 36287@https://legacy.forums.gravityhelp.com/ <p>I'm unable to replicate the problem.</p> <p>screenshot: <a href="http://bit.ly/p6pM4e" rel="nofollow">http://bit.ly/p6pM4e</a></p> <p>Have you added any custom HTML to your form? How about a link to your form page so we can check it out? I'll be happy to take a look and see what I can find out. </p> https://legacy.forums.gravityhelp.com/topic/16rc1-formatting-bug#post-36278 Mon, 26 Sep 2011 19:22:45 +0000 muhromatic 36278@https://legacy.forums.gravityhelp.com/ <p>It seems that the latest version is breaking all <code>&lt;hr /&gt;</code> tags placed below a form regardless of theme.</p> <p>they appear as a short line "float right" above the form.</p> <p>and nothing looks out of place via firebug </p>