<?xml version="1.0" encoding="UTF-8"?>
<!-- generator="bbPress/1.0.1" -->
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>Gravity Support Forums Topic: Browser display variations</title>
		<link>https://legacy.forums.gravityhelp.com/topic/browser-display-variations</link>
		<description>Gravity Support Forums Topic: Browser display variations</description>
		<language>en-US</language>
		<pubDate>Tue, 28 Apr 2026 20:09:27 +0000</pubDate>
		<generator>http://bbpress.org/?v=1.0.1</generator>
		<textInput>
			<title><![CDATA[Search]]></title>
			<description><![CDATA[Search all topics from these forums.]]></description>
			<name>q</name>
			<link>https://legacy.forums.gravityhelp.com/search.php</link>
		</textInput>
		<atom:link href="https://legacy.forums.gravityhelp.com/rss/topic/browser-display-variations" rel="self" type="application/rss+xml" />

		<item>
			<title>Kevin Flahaut on "Browser display variations"</title>
			<link>https://legacy.forums.gravityhelp.com/topic/browser-display-variations#post-33571</link>
			<pubDate>Thu, 25 Aug 2011 16:10:03 +0000</pubDate>
			<dc:creator>Kevin Flahaut</dc:creator>
			<guid isPermaLink="false">33571@https://legacy.forums.gravityhelp.com/</guid>
			<description>&#60;p&#62;Cool. Thanks for the update.&#60;/p&#62;
&#60;p&#62;Edit: We've decided to add a browser class to the form wrapper for the 1.6 version so you'll be able to use that for browser-specific styles in the future. No need to add the other script to use that with Gravity Forms now.
&#60;/p&#62;</description>
		</item>
		<item>
			<title>Colinz on "Browser display variations"</title>
			<link>https://legacy.forums.gravityhelp.com/topic/browser-display-variations#post-33570</link>
			<pubDate>Thu, 25 Aug 2011 16:04:59 +0000</pubDate>
			<dc:creator>Colinz</dc:creator>
			<guid isPermaLink="false">33570@https://legacy.forums.gravityhelp.com/</guid>
			<description>&#60;p&#62;Thank you very much Kevin, that worked nicely. &#60;/p&#62;
&#60;p&#62;I'll tuck that browser specific rule format away for another day....very useful.&#60;/p&#62;
&#60;p&#62;Cheers
&#60;/p&#62;</description>
		</item>
		<item>
			<title>Kevin Flahaut on "Browser display variations"</title>
			<link>https://legacy.forums.gravityhelp.com/topic/browser-display-variations#post-33540</link>
			<pubDate>Thu, 25 Aug 2011 10:09:52 +0000</pubDate>
			<dc:creator>Kevin Flahaut</dc:creator>
			<guid isPermaLink="false">33540@https://legacy.forums.gravityhelp.com/</guid>
			<description>&#60;p&#62;Yep, padding and margins are rendered differently by all the browsers. It's difficult to get everything &#34;spot on&#34; in all the browsers without a few tricks. You will most likely need to define a height on the input.&#60;/p&#62;
&#60;pre&#62;&#60;code&#62;body #gform_wrapper_1.gform_wrapper input[type=text] {
	height:20px
}&#60;/code&#62;&#60;/pre&#62;
&#60;p&#62; screenshot: &#60;a href=&#34;http://bit.ly/oM7cEO&#34; rel=&#34;nofollow&#34;&#62;http://bit.ly/oM7cEO&#60;/a&#62;&#60;/p&#62;
&#60;p&#62;You'll probably need to add some chrome/safari-specific hacks to the CSS to apply different values to different browsers. If you do a quick Google search, you'll find several methods to do this.&#60;/p&#62;
&#60;p&#62;I personally prefer to use this &#34;browser class&#34; snippet added to my WordPress functions file. It appends a browser class to the body element and lets you apply different rules based on inheritance from the body class. That allows you to avoid &#34;hacks&#34; or invalid CSS if that's important to you.&#60;/p&#62;
&#60;p&#62;&#60;a href=&#34;http://www.wprecipes.com/how-to-detect-the-visitor-browser-within-wordpress&#34; rel=&#34;nofollow&#34;&#62;http://www.wprecipes.com/how-to-detect-the-visitor-browser-within-wordpress&#60;/a&#62;&#60;/p&#62;
&#60;p&#62;&#60;a href=&#34;http://www.nathanrice.net/blog/browser-detection-and-the-body_class-function/&#34; rel=&#34;nofollow&#34;&#62;http://www.nathanrice.net/blog/browser-detection-and-the-body_class-function/&#60;/a&#62;&#60;/p&#62;
&#60;p&#62;If you're using that, you could define different values per browser like this..&#60;/p&#62;
&#60;pre&#62;&#60;code&#62;[css]

/* general rule */
body #gform_wrapper_1.gform_wrapper input[type=text] {
	height:18px
}

/* safari-specific rule */
body.safari #gform_wrapper_1.gform_wrapper input[type=text] {
	height:20px
}

/* chrome-specific rule */
body.chrome #gform_wrapper_1.gform_wrapper input[type=text] {
	height:24px
}&#60;/code&#62;&#60;/pre&#62;</description>
		</item>
		<item>
			<title>Colinz on "Browser display variations"</title>
			<link>https://legacy.forums.gravityhelp.com/topic/browser-display-variations#post-33515</link>
			<pubDate>Thu, 25 Aug 2011 00:50:45 +0000</pubDate>
			<dc:creator>Colinz</dc:creator>
			<guid isPermaLink="false">33515@https://legacy.forums.gravityhelp.com/</guid>
			<description>&#60;p&#62;I recently added an email field to a new sites home page and support assisted in formatting. However, having tweaked the field to look satisfactory, l now see that in Chrome and Safari the field box is thicker (as in height) than when viewed in Firefox, making the layout look wrong.&#60;/p&#62;
&#60;p&#62;Can anyone offer any guidance, please?&#60;/p&#62;
&#60;p&#62;&#60;a href=&#34;http://www.foxyladynelson.co.nz/&#34; rel=&#34;nofollow&#34;&#62;http://www.foxyladynelson.co.nz/&#60;/a&#62;&#60;/p&#62;
&#60;p&#62;Cheers&#60;br /&#62;
Colin
&#60;/p&#62;</description>
		</item>

	</channel>
</rss>
