<?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: our known unknowns</title>
	<atom:link href="http://scatter.wordpress.com/2007/11/18/our-known-unknowns/feed/" rel="self" type="application/rss+xml" />
	<link>http://scatter.wordpress.com/2007/11/18/our-known-unknowns/</link>
	<description>the unruly darlings of public sociology</description>
	<pubDate>Sat, 30 Aug 2008 07:04:16 +0000</pubDate>
	<generator>http://wordpress.org/?v=MU</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: mike3550</title>
		<link>http://scatter.wordpress.com/2007/11/18/our-known-unknowns/#comment-70</link>
		<dc:creator>mike3550</dc:creator>
		<pubDate>Mon, 19 Nov 2007 23:24:14 +0000</pubDate>
		<guid isPermaLink="false">http://scatter.wordpress.com/2007/11/18/our-known-unknowns/#comment-70</guid>
		<description>Jeremy, I figured you had already tried what I suggested in the last post (as mbader...), I think that I found a solution:

Enter the following into your .css file:
div#container {
margin: 0 0 0 -300px;
}

div#content {
margin: 0 0 0 300px;
}

div.sidebar {
width: 299px;
}
I &lt;b&gt;think&lt;/b&gt; that will work. 

Also, on getting rid of the header space, I think that decreasing the padding-top of the #access element would work.</description>
		<content:encoded><![CDATA[<p>Jeremy, I figured you had already tried what I suggested in the last post (as mbader&#8230;), I think that I found a solution:</p>
<p>Enter the following into your .css file:<br />
div#container {<br />
margin: 0 0 0 -300px;<br />
}</p>
<p>div#content {<br />
margin: 0 0 0 300px;<br />
}</p>
<p>div.sidebar {<br />
width: 299px;<br />
}<br />
I <b>think</b> that will work. </p>
<p>Also, on getting rid of the header space, I think that decreasing the padding-top of the #access element would work.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: jeremy</title>
		<link>http://scatter.wordpress.com/2007/11/18/our-known-unknowns/#comment-62</link>
		<dc:creator>jeremy</dc:creator>
		<pubDate>Mon, 19 Nov 2007 16:11:10 +0000</pubDate>
		<guid isPermaLink="false">http://scatter.wordpress.com/2007/11/18/our-known-unknowns/#comment-62</guid>
		<description>Additional clues:

1.  I can actually take the margin statements for the #container and #comment out completely and it doesn't affect anything.

2.  If I set width for #secondary to anything above *200* (not 240) the sidebar reverts to the bottom.  If I set it to a low value, like 50, it does indeed squish.</description>
		<content:encoded><![CDATA[<p>Additional clues:</p>
<p>1.  I can actually take the margin statements for the #container and #comment out completely and it doesn&#8217;t affect anything.</p>
<p>2.  If I set width for #secondary to anything above *200* (not 240) the sidebar reverts to the bottom.  If I set it to a low value, like 50, it does indeed squish.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: jeremy</title>
		<link>http://scatter.wordpress.com/2007/11/18/our-known-unknowns/#comment-61</link>
		<dc:creator>jeremy</dc:creator>
		<pubDate>Mon, 19 Nov 2007 16:03:53 +0000</pubDate>
		<guid isPermaLink="false">http://scatter.wordpress.com/2007/11/18/our-known-unknowns/#comment-61</guid>
		<description>jay: I'm certainly glad you took the trouble.  And now that you've taken the trouble, cognitive dissonance theory would predict that you should be *extra* motivated to comment.  I hope it's right!

mbader:  Thanks. I've tried changing the 240s in #container and #content to a higher number, and the main text doesn't move over.  This is where I'm stuck.  Note also that the sidebar being set to 240px is a red herring; that's the primary sidebar, which is actually over on the right and hidden.  The sidebar on the left that is visible is the secondary sidebar.  If I insert a width for the secondary sidebar that is greater than 240--changing the container and content values to the same--the sidebar goes to the bottom.  

I think you are exactly right why it does this, but I can't figure out how to get the main text to move over.</description>
		<content:encoded><![CDATA[<p>jay: I&#8217;m certainly glad you took the trouble.  And now that you&#8217;ve taken the trouble, cognitive dissonance theory would predict that you should be *extra* motivated to comment.  I hope it&#8217;s right!</p>
<p>mbader:  Thanks. I&#8217;ve tried changing the 240s in #container and #content to a higher number, and the main text doesn&#8217;t move over.  This is where I&#8217;m stuck.  Note also that the sidebar being set to 240px is a red herring; that&#8217;s the primary sidebar, which is actually over on the right and hidden.  The sidebar on the left that is visible is the secondary sidebar.  If I insert a width for the secondary sidebar that is greater than 240&#8211;changing the container and content values to the same&#8211;the sidebar goes to the bottom.  </p>
<p>I think you are exactly right why it does this, but I can&#8217;t figure out how to get the main text to move over.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: mbader</title>
		<link>http://scatter.wordpress.com/2007/11/18/our-known-unknowns/#comment-60</link>
		<dc:creator>mbader</dc:creator>
		<pubDate>Mon, 19 Nov 2007 15:32:49 +0000</pubDate>
		<guid isPermaLink="false">http://scatter.wordpress.com/2007/11/18/our-known-unknowns/#comment-60</guid>
		<description>Jeremy, I am sure that you already tried this - and not having a Wordpress.com blog, I am not positive.  However, it looks like in the &lt;a href="http://scatter.wordpress.com/?css=css&#38;rev=0" rel="nofollow"&gt;css&lt;/a&gt;,  the right margin on the #container div is set to -240px, the right margin on the #content div is set to 240px and the width of the sidebar is set to 240px -- if you make the first two divs' margins equal to the same width as you set the sidebar width, I would guess that it would work.  I suspect that because the #content div is set to float left, when the sidebar is widened and the current margins are maintained, it is too wide to fit in the #content div side-by-side with the sidebars, therefore it will float all the way to its left margin and the sidebar will take the space below it. 

But, I can never get these things to work out in what I think  that they are supposed to and it usually takes me about three hours to figure these things out.</description>
		<content:encoded><![CDATA[<p>Jeremy, I am sure that you already tried this - and not having a WordPress.com blog, I am not positive.  However, it looks like in the <a href="http://scatter.wordpress.com/?css=css&amp;rev=0" rel="nofollow">css</a>,  the right margin on the #container div is set to -240px, the right margin on the #content div is set to 240px and the width of the sidebar is set to 240px &#8212; if you make the first two divs&#8217; margins equal to the same width as you set the sidebar width, I would guess that it would work.  I suspect that because the #content div is set to float left, when the sidebar is widened and the current margins are maintained, it is too wide to fit in the #content div side-by-side with the sidebars, therefore it will float all the way to its left margin and the sidebar will take the space below it. </p>
<p>But, I can never get these things to work out in what I think  that they are supposed to and it usually takes me about three hours to figure these things out.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: jaylivingston</title>
		<link>http://scatter.wordpress.com/2007/11/18/our-known-unknowns/#comment-59</link>
		<dc:creator>jaylivingston</dc:creator>
		<pubDate>Mon, 19 Nov 2007 13:06:27 +0000</pubDate>
		<guid isPermaLink="false">http://scatter.wordpress.com/2007/11/18/our-known-unknowns/#comment-59</guid>
		<description>Noncontributors &lt;i&gt;can&lt;/i&gt; comment, but it wasn't easy.  You have to establish a Wordpress ID, and it took me several tries.  First, WP didn't like my password; then they didn't like my user name, and it took me a few tries to figure out that it was because I had a space in it.  Feh.</description>
		<content:encoded><![CDATA[<p>Noncontributors <i>can</i> comment, but it wasn&#8217;t easy.  You have to establish a WordPress ID, and it took me several tries.  First, WP didn&#8217;t like my password; then they didn&#8217;t like my user name, and it took me a few tries to figure out that it was because I had a space in it.  Feh.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
