<?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: Read my article in the Microsoft Expression November Newsletter</title>
	<atom:link href="http://www.designisphilosophy.com/microsoft-expression-web/read-my-article-in-the-microsoft-expression-november-newsletter-20081118/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.designisphilosophy.com/microsoft-expression-web/read-my-article-in-the-microsoft-expression-november-newsletter-20081118/</link>
	<description>Tutorials and thoughts on Microsoft Expression, CSS and WordPress</description>
	<lastBuildDate>Thu, 02 Sep 2010 01:43:32 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
	<item>
		<title>By: Michelle</title>
		<link>http://www.designisphilosophy.com/microsoft-expression-web/read-my-article-in-the-microsoft-expression-november-newsletter-20081118/comment-page-1/#comment-65839</link>
		<dc:creator>Michelle</dc:creator>
		<pubDate>Fri, 06 Nov 2009 00:34:57 +0000</pubDate>
		<guid isPermaLink="false">http://blog.pinkandyellow.com/?p=186#comment-65839</guid>
		<description>thx for the awesome tutorial.keep them coming..</description>
		<content:encoded><![CDATA[<p>thx for the awesome tutorial.keep them coming..</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jennifer</title>
		<link>http://www.designisphilosophy.com/microsoft-expression-web/read-my-article-in-the-microsoft-expression-november-newsletter-20081118/comment-page-1/#comment-65836</link>
		<dc:creator>Jennifer</dc:creator>
		<pubDate>Fri, 06 Nov 2009 00:24:27 +0000</pubDate>
		<guid isPermaLink="false">http://blog.pinkandyellow.com/?p=186#comment-65836</guid>
		<description>Very, very interesting post.Thx.</description>
		<content:encoded><![CDATA[<p>Very, very interesting post.Thx.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: John Hampton</title>
		<link>http://www.designisphilosophy.com/microsoft-expression-web/read-my-article-in-the-microsoft-expression-november-newsletter-20081118/comment-page-1/#comment-23971</link>
		<dc:creator>John Hampton</dc:creator>
		<pubDate>Sat, 10 Jan 2009 21:22:44 +0000</pubDate>
		<guid isPermaLink="false">http://blog.pinkandyellow.com/?p=186#comment-23971</guid>
		<description>hi
1u86u8rv9a2vfj0c
good luck</description>
		<content:encoded><![CDATA[<p>hi<br />
1u86u8rv9a2vfj0c<br />
good luck</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Richard Stricker</title>
		<link>http://www.designisphilosophy.com/microsoft-expression-web/read-my-article-in-the-microsoft-expression-november-newsletter-20081118/comment-page-1/#comment-20594</link>
		<dc:creator>Richard Stricker</dc:creator>
		<pubDate>Mon, 24 Nov 2008 05:38:58 +0000</pubDate>
		<guid isPermaLink="false">http://blog.pinkandyellow.com/?p=186#comment-20594</guid>
		<description>Please let me know what you find out. I want to do this the right way.

R</description>
		<content:encoded><![CDATA[<p>Please let me know what you find out. I want to do this the right way.</p>
<p>R</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Morten Rand-Hendriksen</title>
		<link>http://www.designisphilosophy.com/microsoft-expression-web/read-my-article-in-the-microsoft-expression-november-newsletter-20081118/comment-page-1/#comment-20568</link>
		<dc:creator>Morten Rand-Hendriksen</dc:creator>
		<pubDate>Sun, 23 Nov 2008 20:40:19 +0000</pubDate>
		<guid isPermaLink="false">http://blog.pinkandyellow.com/?p=186#comment-20568</guid>
		<description>IE8 is still not in its final release so it is quite possible that it doesn&#039;t handle the visibility attribute properly. It is a little weird though because the whole point of IE8 is that it is supposed to be standards compliant, and the visibility method is standards compliant. I have to check it myself to see what you are talking about. too curious.</description>
		<content:encoded><![CDATA[<p>IE8 is still not in its final release so it is quite possible that it doesn&#8217;t handle the visibility attribute properly. It is a little weird though because the whole point of IE8 is that it is supposed to be standards compliant, and the visibility method is standards compliant. I have to check it myself to see what you are talking about. too curious.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Richard Stricker</title>
		<link>http://www.designisphilosophy.com/microsoft-expression-web/read-my-article-in-the-microsoft-expression-november-newsletter-20081118/comment-page-1/#comment-20475</link>
		<dc:creator>Richard Stricker</dc:creator>
		<pubDate>Sat, 22 Nov 2008 21:52:45 +0000</pubDate>
		<guid isPermaLink="false">http://blog.pinkandyellow.com/?p=186#comment-20475</guid>
		<description>Hi Morten, thanks for helping me untangle my coding. I posted both versions of the menu on my site. www.skystonemedia.com (look for the link on my Contact page).

Your point about Opera is well taken, and provided another clue. I am using IE8 and the visibility method doesn&#039;t seem to work very well. But when I use &quot;compatiblitiy mode&quot;, both versions work as expected. 

I liked your comment about coding for IE6 (like distributing on VHS because not everyone has a DVD player). I hope the compatiblity issues can someday be resolved and level the field for different browsers. Until then, is it all &quot;hit or miss&quot; without extreme coding? The idea of trying to accommodate every browser seems daunting (for a non-commercial site). 

By the way, on one of the menus is a link to some primitive Blend/Encoder stuff. Maybe could give you an idea for another Expression newsletter project. I do enjoy and learn from your tutorials.

RIchard</description>
		<content:encoded><![CDATA[<p>Hi Morten, thanks for helping me untangle my coding. I posted both versions of the menu on my site. <a href="http://www.skystonemedia.com" rel="nofollow">http://www.skystonemedia.com</a> (look for the link on my Contact page).</p>
<p>Your point about Opera is well taken, and provided another clue. I am using IE8 and the visibility method doesn&#8217;t seem to work very well. But when I use &#8220;compatiblitiy mode&#8221;, both versions work as expected. </p>
<p>I liked your comment about coding for IE6 (like distributing on VHS because not everyone has a DVD player). I hope the compatiblity issues can someday be resolved and level the field for different browsers. Until then, is it all &#8220;hit or miss&#8221; without extreme coding? The idea of trying to accommodate every browser seems daunting (for a non-commercial site). </p>
<p>By the way, on one of the menus is a link to some primitive Blend/Encoder stuff. Maybe could give you an idea for another Expression newsletter project. I do enjoy and learn from your tutorials.</p>
<p>RIchard</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Morten Rand-Hendriksen</title>
		<link>http://www.designisphilosophy.com/microsoft-expression-web/read-my-article-in-the-microsoft-expression-november-newsletter-20081118/comment-page-1/#comment-20419</link>
		<dc:creator>Morten Rand-Hendriksen</dc:creator>
		<pubDate>Sat, 22 Nov 2008 06:35:10 +0000</pubDate>
		<guid isPermaLink="false">http://blog.pinkandyellow.com/?p=186#comment-20419</guid>
		<description>Hi Richard. I&#039;ll split this answer in half:

In the first comment you mention that when you got the menu items to drop down the text didn&#039;t show until you hovered over the items. The only way I can imagine that would happen would be if your text colour matched the background colour for the non-hover state. There is no code in the tutorial that hides the text in any other way. I&#039;d like to see your code to see what is going on. I&#039;m a curious guy.

To your second point about using display instead of visibility to hide the drop-down menu: Test your menu in Opera. Opera is a very &quot;unforgiving&quot; browser - in other words it is a bit of a stickler for proper code. You&#039;ll see that when you use the block technique, the drop-down areas leave remnants after being collapsed. This is because you are not actually hiding the drop-down portions but instead refusing to define an area for them to occupy. This works most of the time but can also lead to some weird results.

The display technique may work but is not as safe as the visibility technique.

Glad to see you are learning something from my tutorial. Feel free to ask any other questions that may arise. I&#039;m always ready for a challenge!</description>
		<content:encoded><![CDATA[<p>Hi Richard. I&#8217;ll split this answer in half:</p>
<p>In the first comment you mention that when you got the menu items to drop down the text didn&#8217;t show until you hovered over the items. The only way I can imagine that would happen would be if your text colour matched the background colour for the non-hover state. There is no code in the tutorial that hides the text in any other way. I&#8217;d like to see your code to see what is going on. I&#8217;m a curious guy.</p>
<p>To your second point about using display instead of visibility to hide the drop-down menu: Test your menu in Opera. Opera is a very &#8220;unforgiving&#8221; browser &#8211; in other words it is a bit of a stickler for proper code. You&#8217;ll see that when you use the block technique, the drop-down areas leave remnants after being collapsed. This is because you are not actually hiding the drop-down portions but instead refusing to define an area for them to occupy. This works most of the time but can also lead to some weird results.</p>
<p>The display technique may work but is not as safe as the visibility technique.</p>
<p>Glad to see you are learning something from my tutorial. Feel free to ask any other questions that may arise. I&#8217;m always ready for a challenge!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Richard Stricker</title>
		<link>http://www.designisphilosophy.com/microsoft-expression-web/read-my-article-in-the-microsoft-expression-november-newsletter-20081118/comment-page-1/#comment-20410</link>
		<dc:creator>Richard Stricker</dc:creator>
		<pubDate>Sat, 22 Nov 2008 04:19:22 +0000</pubDate>
		<guid isPermaLink="false">http://blog.pinkandyellow.com/?p=186#comment-20410</guid>
		<description>okay. Trying to share code is harder than it looks. I retried the change I found above and it didn&#039;t work anymore. I had found the display block change idea in the &quot;coffee break training section&quot; of the expression newsletter under another version of the &quot;Creating Standards Based Drop Down Menus&quot;, but I had missed a part of the instructions.

By relating the codes in the &quot;hide&quot; and &quot;show&quot; sections, it seems to be working again. 

ul li ul {
	
	display: none;
}
ul li:hover ul {
	display: block;
	
}

Sorry for any confusion I may have scattered.

Richard (coding at the &quot;hopes this works&quot; level)</description>
		<content:encoded><![CDATA[<p>okay. Trying to share code is harder than it looks. I retried the change I found above and it didn&#8217;t work anymore. I had found the display block change idea in the &#8220;coffee break training section&#8221; of the expression newsletter under another version of the &#8220;Creating Standards Based Drop Down Menus&#8221;, but I had missed a part of the instructions.</p>
<p>By relating the codes in the &#8220;hide&#8221; and &#8220;show&#8221; sections, it seems to be working again. </p>
<p>ul li ul {</p>
<p>	display: none;<br />
}<br />
ul li:hover ul {<br />
	display: block;</p>
<p>}</p>
<p>Sorry for any confusion I may have scattered.</p>
<p>Richard (coding at the &#8220;hopes this works&#8221; level)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Richard Stricker</title>
		<link>http://www.designisphilosophy.com/microsoft-expression-web/read-my-article-in-the-microsoft-expression-november-newsletter-20081118/comment-page-1/#comment-20405</link>
		<dc:creator>Richard Stricker</dc:creator>
		<pubDate>Sat, 22 Nov 2008 03:29:02 +0000</pubDate>
		<guid isPermaLink="false">http://blog.pinkandyellow.com/?p=186#comment-20405</guid>
		<description>Thanks for setting this back in place. As a beginning css writer I find that I need every i dotted as I laboriously code from one line to the next. In a way, I learn even when the code doesn&#039;t work, it makes me try some other ideas and look more closely at the processes. So thanks for an article that pulled me beyond my comfort zone, that helps.

Once I had the display to block handled the menu worked, pretty well. However, when I would hover over the main menu item, the drop down would drop down, but without text until I moused over the drop down list items themselves. Then they would show the text.

I can only imagine what it must be like to include EVERY step in a long sequence (especially one that is put up somewhere else). By combining some sources I came across that Block Display feature again. 

When the mouseover triggers the &quot;a&quot; instead of making the link &quot;visible&quot; it seems to work better if it triggers &quot;block display&quot;. Now the drop down is smooth. 

ul li:hover ul {
	visibility: visible;
	background-color: ;
	display: block;
}

Thanks again for helping me with expression web and css. Motivating a newbie to try something is big, and appreciated. I look forward to the next installment.

Richard</description>
		<content:encoded><![CDATA[<p>Thanks for setting this back in place. As a beginning css writer I find that I need every i dotted as I laboriously code from one line to the next. In a way, I learn even when the code doesn&#8217;t work, it makes me try some other ideas and look more closely at the processes. So thanks for an article that pulled me beyond my comfort zone, that helps.</p>
<p>Once I had the display to block handled the menu worked, pretty well. However, when I would hover over the main menu item, the drop down would drop down, but without text until I moused over the drop down list items themselves. Then they would show the text.</p>
<p>I can only imagine what it must be like to include EVERY step in a long sequence (especially one that is put up somewhere else). By combining some sources I came across that Block Display feature again. </p>
<p>When the mouseover triggers the &#8220;a&#8221; instead of making the link &#8220;visible&#8221; it seems to work better if it triggers &#8220;block display&#8221;. Now the drop down is smooth. </p>
<p>ul li:hover ul {<br />
	visibility: visible;<br />
	background-color: ;<br />
	display: block;<br />
}</p>
<p>Thanks again for helping me with expression web and css. Motivating a newbie to try something is big, and appreciated. I look forward to the next installment.</p>
<p>Richard</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Morten Rand-Hendriksen</title>
		<link>http://www.designisphilosophy.com/microsoft-expression-web/read-my-article-in-the-microsoft-expression-november-newsletter-20081118/comment-page-1/#comment-20336</link>
		<dc:creator>Morten Rand-Hendriksen</dc:creator>
		<pubDate>Fri, 21 Nov 2008 07:57:55 +0000</pubDate>
		<guid isPermaLink="false">http://blog.pinkandyellow.com/?p=186#comment-20336</guid>
		<description>Richard:

You are actually just missing one line of code: You have to set the display attribute of the anchor as &quot;block&quot;, otherwise it gets treated as an inline element. So, in &lt;em&gt;ul li a&lt;/em&gt; add &quot;display: block;&quot; and you are good to go.

You can find a full working version of the menu &lt;a href=&quot;http://pinkandyellow.com/tutorials/menu.html&quot; rel=&quot;nofollow&quot;&gt;here&lt;/a&gt; and it&#039;s CSS &lt;a href=&quot;http://pinkandyellow.com/tutorials/drop-down.css&quot; rel=&quot;nofollow&quot;&gt;here&lt;/a&gt; for reference.</description>
		<content:encoded><![CDATA[<p>Richard:</p>
<p>You are actually just missing one line of code: You have to set the display attribute of the anchor as &#8220;block&#8221;, otherwise it gets treated as an inline element. So, in <em>ul li a</em> add &#8220;display: block;&#8221; and you are good to go.</p>
<p>You can find a full working version of the menu <a href="http://pinkandyellow.com/tutorials/menu.html" rel="nofollow">here</a> and it&#8217;s CSS <a href="http://pinkandyellow.com/tutorials/drop-down.css" rel="nofollow">here</a> for reference.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
