<?xml version="1.0" encoding="UTF-8"?><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"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Two-Sided Expanding Headers</title>
	<atom:link href="http://manisheriar.com/blog/two-sided-expanding-headers/feed" rel="self" type="application/rss+xml" />
	<link>http://manisheriar.com/blog/two-sided-expanding-headers</link>
	<description>Impeccable Code &#124; Beautiful Design</description>
	<lastBuildDate>Thu, 13 May 2010 19:08:51 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Ed Diehl</title>
		<link>http://manisheriar.com/blog/two-sided-expanding-headers/comment-page-1#comment-13954</link>
		<dc:creator>Ed Diehl</dc:creator>
		<pubDate>Fri, 16 Feb 2007 12:47:40 +0000</pubDate>
		<guid isPermaLink="false">http://manisheriar.com/blog/two-sided-expanding-headers#comment-13954</guid>
		<description>Working with your expanding header was exactly what I was looking for, except for one thing: I am using Project Seven&#039;s CSS Express menus (url:http://www.projectseven.com/tutorials/navigation/auto_hide/index.htm) combined with their 3-column fluid body content, and the  tags prevent the menu from displaying at all. I&#039;ve tried various configurations for placement, but nothing has worked yet. The usual result is that the graphics display behind the 3-columns, and the navbar disappears. If the navbar is visible, it does not function.

Suggestions?

Best regards,
Ed</description>
		<content:encoded><![CDATA[<p>Working with your expanding header was exactly what I was looking for, except for one thing: I am using Project Seven&#8217;s CSS Express menus (url:<a href="http://www.projectseven.com/tutorials/navigation/auto_hide/index.htm" rel="nofollow">http://www.projectseven.com/tutorials/navigation/auto_hide/index.htm</a>) combined with their 3-column fluid body content, and the  tags prevent the menu from displaying at all. I&#8217;ve tried various configurations for placement, but nothing has worked yet. The usual result is that the graphics display behind the 3-columns, and the navbar disappears. If the navbar is visible, it does not function.</p>
<p>Suggestions?</p>
<p>Best regards,<br />
Ed</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Candy</title>
		<link>http://manisheriar.com/blog/two-sided-expanding-headers/comment-page-1#comment-2714</link>
		<dc:creator>Candy</dc:creator>
		<pubDate>Tue, 26 Sep 2006 17:54:59 +0000</pubDate>
		<guid isPermaLink="false">http://manisheriar.com/blog/two-sided-expanding-headers#comment-2714</guid>
		<description>This was really helpful to me, I have been struggling with a similar issue for a while now!
Also, any tips for bottom borders? As in, the same as this but running across the bottom of the page. Mine always jumps up and never stays put!</description>
		<content:encoded><![CDATA[<p>This was really helpful to me, I have been struggling with a similar issue for a while now!<br />
Also, any tips for bottom borders? As in, the same as this but running across the bottom of the page. Mine always jumps up and never stays put!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Andy</title>
		<link>http://manisheriar.com/blog/two-sided-expanding-headers/comment-page-1#comment-510</link>
		<dc:creator>Andy</dc:creator>
		<pubDate>Wed, 17 May 2006 23:16:35 +0000</pubDate>
		<guid isPermaLink="false">http://manisheriar.com/blog/two-sided-expanding-headers#comment-510</guid>
		<description>Of course!  I didn&#039;t consider the unstyled display.</description>
		<content:encoded><![CDATA[<p>Of course!  I didn&#8217;t consider the unstyled display.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sheriar Designs</title>
		<link>http://manisheriar.com/blog/two-sided-expanding-headers/comment-page-1#comment-509</link>
		<dc:creator>Sheriar Designs</dc:creator>
		<pubDate>Wed, 17 May 2006 21:46:16 +0000</pubDate>
		<guid isPermaLink="false">http://manisheriar.com/blog/two-sided-expanding-headers#comment-509</guid>
		<description>&lt;strong&gt;Andy:&lt;/strong&gt; I used spans because I don&#039;t want these containers to interfere with spacing if the site were viewed unstyled (like on a handheld device).

Empty spans take up no space at all, whereas empty divs will cause line breaks.</description>
		<content:encoded><![CDATA[<p><strong>Andy:</strong> I used spans because I don&#8217;t want these containers to interfere with spacing if the site were viewed unstyled (like on a handheld device).</p>
<p>Empty spans take up no space at all, whereas empty divs will cause line breaks.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Andy</title>
		<link>http://manisheriar.com/blog/two-sided-expanding-headers/comment-page-1#comment-508</link>
		<dc:creator>Andy</dc:creator>
		<pubDate>Wed, 17 May 2006 21:42:52 +0000</pubDate>
		<guid isPermaLink="false">http://manisheriar.com/blog/two-sided-expanding-headers#comment-508</guid>
		<description>Nice solution to this one.

Is there a reason you use spans instead of divs for the two repeater areas?  Seems to me that a div already has the block level setting, and would thus remove one line of css code from each definition.</description>
		<content:encoded><![CDATA[<p>Nice solution to this one.</p>
<p>Is there a reason you use spans instead of divs for the two repeater areas?  Seems to me that a div already has the block level setting, and would thus remove one line of css code from each definition.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sheriar Designs</title>
		<link>http://manisheriar.com/blog/two-sided-expanding-headers/comment-page-1#comment-504</link>
		<dc:creator>Sheriar Designs</dc:creator>
		<pubDate>Tue, 16 May 2006 18:06:22 +0000</pubDate>
		<guid isPermaLink="false">http://manisheriar.com/blog/two-sided-expanding-headers#comment-504</guid>
		<description>&lt;strong&gt;David:&lt;/strong&gt; Ah ... you&#039;re such a ball buster!  (And I say that with love)  ;o)

Let me say again: I did not design this site.  I am simply coding it.  I have no control over the choice to design for a 1024px window.  But, having said that, many sites are going that way now and I expect more will follow.  I have yet to design one optimized for that width, however.

Yes, &quot;young and hip&quot; may indeed browse with handheld devices, and sites I code are always done with that in mind, as will this one be.  Just because it&#039;s graphical presentation will be wide, that has absolutely no effect on the unstyled document.</description>
		<content:encoded><![CDATA[<p><strong>David:</strong> Ah &#8230; you&#8217;re such a ball buster!  (And I say that with love)  ;o)</p>
<p>Let me say again: I did not design this site.  I am simply coding it.  I have no control over the choice to design for a 1024px window.  But, having said that, many sites are going that way now and I expect more will follow.  I have yet to design one optimized for that width, however.</p>
<p>Yes, &#8220;young and hip&#8221; may indeed browse with handheld devices, and sites I code are always done with that in mind, as will this one be.  Just because it&#8217;s graphical presentation will be wide, that has absolutely no effect on the unstyled document.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: David Hucklesby</title>
		<link>http://manisheriar.com/blog/two-sided-expanding-headers/comment-page-1#comment-503</link>
		<dc:creator>David Hucklesby</dc:creator>
		<pubDate>Tue, 16 May 2006 17:59:46 +0000</pubDate>
		<guid isPermaLink="false">http://manisheriar.com/blog/two-sided-expanding-headers#comment-503</guid>
		<description>&lt;strong&gt;Mani:&lt;/strong&gt; You say:
The page is designed ... for a 1024px width browser

A 1024px screen does not equate to a &quot;1024px width browser&quot;. Consider these cases:

- Browser is not maximized
- Windows taskbar is to the side
- Browser sidebar is open
- A browser toolbar is on one side

&quot;Young and hip&quot; may prefer handheld devices to PCs anyway, if trends in Japan and Europe are an indication.</description>
		<content:encoded><![CDATA[<p><strong>Mani:</strong> You say:<br />
The page is designed &#8230; for a 1024px width browser</p>
<p>A 1024px screen does not equate to a &#8220;1024px width browser&#8221;. Consider these cases:</p>
<p>- Browser is not maximized<br />
- Windows taskbar is to the side<br />
- Browser sidebar is open<br />
- A browser toolbar is on one side</p>
<p>&#8220;Young and hip&#8221; may prefer handheld devices to PCs anyway, if trends in Japan and Europe are an indication.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sheriar Designs</title>
		<link>http://manisheriar.com/blog/two-sided-expanding-headers/comment-page-1#comment-501</link>
		<dc:creator>Sheriar Designs</dc:creator>
		<pubDate>Mon, 15 May 2006 21:23:22 +0000</pubDate>
		<guid isPermaLink="false">http://manisheriar.com/blog/two-sided-expanding-headers#comment-501</guid>
		<description>&lt;strong&gt;David:&lt;/strong&gt; The page is designed (not by me, by the way) for a 1024px width browser (the most common these days), with all the main central content viewable within an 800px wide browser.  That&#039;s why the scroll is there if your browswer is smaller, and there is nothing to do about that.  However, I believe that this method would shrink just fine if the content didn&#039;t force the width (see &lt;a href=&quot;http://manisheriar.com/natural_high/header1.htm&quot; rel=&quot;nofollow&quot;&gt;example 1&lt;/a&gt;, which shows the technique without added content).

As for the nav images not being visible with images turned off, you&#039;re right.  But I&#039;m willing to live with that as they are visible as text when css is disabled, and I think it is a rare thing for folks to be on a browser with images disabled and css enabled.  Especially for this client&#039;s target audience (young and hip).</description>
		<content:encoded><![CDATA[<p><strong>David:</strong> The page is designed (not by me, by the way) for a 1024px width browser (the most common these days), with all the main central content viewable within an 800px wide browser.  That&#8217;s why the scroll is there if your browswer is smaller, and there is nothing to do about that.  However, I believe that this method would shrink just fine if the content didn&#8217;t force the width (see <a href="http://manisheriar.com/natural_high/header1.htm" rel="nofollow">example 1</a>, which shows the technique without added content).</p>
<p>As for the nav images not being visible with images turned off, you&#8217;re right.  But I&#8217;m willing to live with that as they are visible as text when css is disabled, and I think it is a rare thing for folks to be on a browser with images disabled and css enabled.  Especially for this client&#8217;s target audience (young and hip).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: David Hucklesby</title>
		<link>http://manisheriar.com/blog/two-sided-expanding-headers/comment-page-1#comment-500</link>
		<dc:creator>David Hucklesby</dc:creator>
		<pubDate>Mon, 15 May 2006 20:01:11 +0000</pubDate>
		<guid isPermaLink="false">http://manisheriar.com/blog/two-sided-expanding-headers#comment-500</guid>
		<description>Expand - yes. Shrink - no. I&#039;d expect a large number of visitors still experience a horizontal scroll. Could you make the minimum width smaller?

Did you try PNG instead of JPG for the original wide image?

A heads up - the secondary links don&#039;t show with images disabled, or on text browsers. They show up fine in small screen mode, though.

Cordially, David.</description>
		<content:encoded><![CDATA[<p>Expand &#8211; yes. Shrink &#8211; no. I&#8217;d expect a large number of visitors still experience a horizontal scroll. Could you make the minimum width smaller?</p>
<p>Did you try PNG instead of JPG for the original wide image?</p>
<p>A heads up &#8211; the secondary links don&#8217;t show with images disabled, or on text browsers. They show up fine in small screen mode, though.</p>
<p>Cordially, David.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sheriar Designs</title>
		<link>http://manisheriar.com/blog/two-sided-expanding-headers/comment-page-1#comment-499</link>
		<dc:creator>Sheriar Designs</dc:creator>
		<pubDate>Mon, 15 May 2006 02:42:46 +0000</pubDate>
		<guid isPermaLink="false">http://manisheriar.com/blog/two-sided-expanding-headers#comment-499</guid>
		<description>The *{margin:0;pading:0;} resets the margin and padding for &lt;strong&gt;ALL&lt;/strong&gt; elements.  I do this because different browsers have various default margin and padding for elements, which can cause layout discrepencies.  If the margin and padding of all elements is reset to 0 then you will have the opportunity to set them all to whatever you like and be sure that the results will be the same among all browsers.

So, if you use this method, you will have to reset the margins for paragraphs, as well as for all other elements.

Hope this helps!</description>
		<content:encoded><![CDATA[<p>The *{margin:0;pading:0;} resets the margin and padding for <strong>ALL</strong> elements.  I do this because different browsers have various default margin and padding for elements, which can cause layout discrepencies.  If the margin and padding of all elements is reset to 0 then you will have the opportunity to set them all to whatever you like and be sure that the results will be the same among all browsers.</p>
<p>So, if you use this method, you will have to reset the margins for paragraphs, as well as for all other elements.</p>
<p>Hope this helps!</p>
]]></content:encoded>
	</item>
</channel>
</rss>

