<?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: CSS Line Break Bug (screencast)</title> <atom:link href="http://brenelz.com/blog/css-line-break-bug-screencast/feed/" rel="self" type="application/rss+xml" /><link>http://brenelz.com/blog/css-line-break-bug-screencast/</link> <description>a winnipeg website design company.</description> <lastBuildDate>Mon, 06 Feb 2012 15:07:39 +0000</lastBuildDate> <sy:updatePeriod>hourly</sy:updatePeriod> <sy:updateFrequency>1</sy:updateFrequency> <generator>http://wordpress.org/?v=3.3.1</generator> <xhtml:meta xmlns:xhtml="http://www.w3.org/1999/xhtml" name="robots" content="noindex" /> <item><title>By: Joseph S.</title><link>http://brenelz.com/blog/css-line-break-bug-screencast/comment-page-1/#comment-1277</link> <dc:creator>Joseph S.</dc:creator> <pubDate>Wed, 22 Apr 2009 14:51:00 +0000</pubDate> <guid isPermaLink="false">http://www.brenelz.com/blog/?p=934#comment-1277</guid> <description>Yeah, Snookerman, that&#039;s what I thought immediately. When you leave a space in your code between inline elements it will be rendered as one space... just as if you placed a bunch of nbspc between them it would add extra spaces. It is the idea in our head of how li elements should behave as block level that would make this behavior unexpected.</description> <content:encoded><![CDATA[<p>Yeah, Snookerman, that&#8217;s what I thought immediately. When you leave a space in your code between inline elements it will be rendered as one space&#8230; just as if you placed a bunch of nbspc between them it would add extra spaces. It is the idea in our head of how li elements should behave as block level that would make this behavior unexpected.</p> ]]></content:encoded> </item> <item><title>By: kevinMario</title><link>http://brenelz.com/blog/css-line-break-bug-screencast/comment-page-1/#comment-1276</link> <dc:creator>kevinMario</dc:creator> <pubDate>Wed, 22 Apr 2009 02:23:55 +0000</pubDate> <guid isPermaLink="false">http://www.brenelz.com/blog/?p=934#comment-1276</guid> <description>Hope this could explain better : http://www.lunarist.com/files/line_bug_solution.jpgThen again I have to concur to one of the posters above for you just to set LI elements to float:Left and set the UL to overflow:hidden ( float container trick ) and everything should be sweet.</description> <content:encoded><![CDATA[<p>Hope this could explain better :<br /> <a href="http://www.lunarist.com/files/line_bug_solution.jpg" rel="nofollow">http://www.lunarist.com/files/line_bug_solution.jpg</a></p><p>Then again I have to concur to one of the posters above for you just to set LI elements to float:Left and set the UL to overflow:hidden ( float container trick ) and everything should be sweet.</p> ]]></content:encoded> </item> <item><title>By: kevinMario</title><link>http://brenelz.com/blog/css-line-break-bug-screencast/comment-page-1/#comment-1275</link> <dc:creator>kevinMario</dc:creator> <pubDate>Wed, 22 Apr 2009 02:15:46 +0000</pubDate> <guid isPermaLink="false">http://www.brenelz.com/blog/?p=934#comment-1275</guid> <description>Use SHIFT+CTRL+J in Dreamweaver and &#039;fold&#039; your code as often as you can, make sure spaces between the codes are all white (e.g no blue spaces)The easiest way to do this is to fold your BODY tag and then inspect your code. The cleaner it looks the better it is.I&#039;ll post a screenshot to show you what i mean in a sec</description> <content:encoded><![CDATA[<p>Use SHIFT+CTRL+J in Dreamweaver and &#8216;fold&#8217; your code as often as you can, make sure spaces between the codes are all white (e.g no blue spaces)</p><p>The easiest way to do this is to fold your BODY tag and then inspect your code. The cleaner it looks the better it is.</p><p>I&#8217;ll post a screenshot to show you what i mean in a sec</p> ]]></content:encoded> </item> <item><title>By: Brenley Dueck</title><link>http://brenelz.com/blog/css-line-break-bug-screencast/comment-page-1/#comment-1274</link> <dc:creator>Brenley Dueck</dc:creator> <pubDate>Tue, 21 Apr 2009 21:29:30 +0000</pubDate> <guid isPermaLink="false">http://www.brenelz.com/blog/?p=934#comment-1274</guid> <description>Good tips snookerman... I don&#039;t really have all the answers... but wanted to point out the problem anyways.</description> <content:encoded><![CDATA[<p>Good tips snookerman&#8230; I don&#8217;t really have all the answers&#8230; but wanted to point out the problem anyways.</p> ]]></content:encoded> </item> <item><title>By: Snookerman</title><link>http://brenelz.com/blog/css-line-break-bug-screencast/comment-page-1/#comment-1273</link> <dc:creator>Snookerman</dc:creator> <pubDate>Tue, 21 Apr 2009 21:20:53 +0000</pubDate> <guid isPermaLink="false">http://www.brenelz.com/blog/?p=934#comment-1273</guid> <description>In the above example I actually had a lot of space between the first two hellos and only one space between the second pair. The browser immediately ignored all spaces except one. Just as expected.</description> <content:encoded><![CDATA[<p>In the above example I actually had a lot of space between the first two hellos and only one space between the second pair. The browser immediately ignored all spaces except one. Just as expected.</p> ]]></content:encoded> </item> <item><title>By: Snookerman</title><link>http://brenelz.com/blog/css-line-break-bug-screencast/comment-page-1/#comment-1272</link> <dc:creator>Snookerman</dc:creator> <pubDate>Tue, 21 Apr 2009 21:18:12 +0000</pubDate> <guid isPermaLink="false">http://www.brenelz.com/blog/?p=934#comment-1272</guid> <description>This is a better explanation maybe, if you put two anchor links after each other in a text, for example &lt;a href=&quot;site&quot; rel=&quot;nofollow&quot;&gt;site&lt;/a&gt; &lt;a href=&quot;site&quot; rel=&quot;nofollow&quot;&gt;site&lt;/a&gt; you expect the space between them to be rendered, and it is. If you put more than one space, or like in your example, a line break and some tabs, the browser will still only display a space and ignore the rest. It even happens in normal text. This: hello            hello is the same as: hello helloYou can try it in your examples, leave only one space between the problematic elements and you will see the same space.This is definitely not a bug, it&#039;s just expected behaviour that you have totally misunderstood.</description> <content:encoded><![CDATA[<p>This is a better explanation maybe, if you put two anchor links after each other in a text, for example <a href="site" rel="nofollow">site</a> <a href="site" rel="nofollow">site</a> you expect the space between them to be rendered, and it is. If you put more than one space, or like in your example, a line break and some tabs, the browser will still only display a space and ignore the rest. It even happens in normal text. This:<br /> hello            hello<br /> is the same as:<br /> hello hello</p><p>You can try it in your examples, leave only one space between the problematic elements and you will see the same space.</p><p>This is definitely not a bug, it&#8217;s just expected behaviour that you have totally misunderstood.</p> ]]></content:encoded> </item> <item><title>By: Snookerman</title><link>http://brenelz.com/blog/css-line-break-bug-screencast/comment-page-1/#comment-1271</link> <dc:creator>Snookerman</dc:creator> <pubDate>Tue, 21 Apr 2009 21:08:02 +0000</pubDate> <guid isPermaLink="false">http://www.brenelz.com/blog/?p=934#comment-1271</guid> <description>This is not a bug. If you have a line break or a lot of whitespace between inline elements, the browser will only show one space. That is why you should put anchor tags right after each other or image tags. If you make list items or divs act like inline elements, they will follow the same rules.</description> <content:encoded><![CDATA[<p>This is not a bug. If you have a line break or a lot of whitespace between inline elements, the browser will only show one space. That is why you should put anchor tags right after each other or image tags. If you make list items or divs act like inline elements, they will follow the same rules.</p> ]]></content:encoded> </item> <item><title>By: Paperboy</title><link>http://brenelz.com/blog/css-line-break-bug-screencast/comment-page-1/#comment-1270</link> <dc:creator>Paperboy</dc:creator> <pubDate>Tue, 21 Apr 2009 17:54:49 +0000</pubDate> <guid isPermaLink="false">http://www.brenelz.com/blog/?p=934#comment-1270</guid> <description>I remember having these problems (with images) too. And it sure took a while before I found the solution!Thanks for the reminder!</description> <content:encoded><![CDATA[<p>I remember having these problems (with images) too. And it sure took a while before I found the solution!</p><p>Thanks for the reminder!</p> ]]></content:encoded> </item> <item><title>By: Ian</title><link>http://brenelz.com/blog/css-line-break-bug-screencast/comment-page-1/#comment-1282</link> <dc:creator>Ian</dc:creator> <pubDate>Mon, 20 Apr 2009 14:41:16 +0000</pubDate> <guid isPermaLink="false">http://www.brenelz.com/blog/?p=934#comment-1282</guid> <description>You really probably shuldn&#039;t convert the elements to inline, because then you lose all sorts of support for margins and padding. As well making your code clump up makes it less pleasant to work with.A more elegant solution is to set the elements to Float: left/right and adjust from there. You can even set the list items to float and the anchors to display: block for maximum control.The float option does have some of its own pitfalls, but as long as you apply them carefully and use clear: both on your contrainer blocks you will be fine.</description> <content:encoded><![CDATA[<p>You really probably shuldn&#8217;t convert the elements to inline, because then you lose all sorts of support for margins and padding. As well making your code clump up makes it less pleasant to work with.</p><p>A more elegant solution is to set the elements to Float: left/right and adjust from there. You can even set the list items to float and the anchors to display: block for maximum control.</p><p>The float option does have some of its own pitfalls, but as long as you apply them carefully and use clear: both on your contrainer blocks you will be fine.</p> ]]></content:encoded> </item> <item><title>By: shane sponagle</title><link>http://brenelz.com/blog/css-line-break-bug-screencast/comment-page-1/#comment-1278</link> <dc:creator>shane sponagle</dc:creator> <pubDate>Sat, 18 Apr 2009 19:24:01 +0000</pubDate> <guid isPermaLink="false">http://www.brenelz.com/blog/?p=934#comment-1278</guid> <description>Cool tip. Don&#039;t remember having this problem before, but now I am ready for it if it does show up. Thanks</description> <content:encoded><![CDATA[<p>Cool tip. Don&#8217;t remember having this problem before, but now I am ready for it if it does show up. Thanks</p> ]]></content:encoded> </item> <item><title>By: Meshach</title><link>http://brenelz.com/blog/css-line-break-bug-screencast/comment-page-1/#comment-1279</link> <dc:creator>Meshach</dc:creator> <pubDate>Sat, 18 Apr 2009 16:03:07 +0000</pubDate> <guid isPermaLink="false">http://www.brenelz.com/blog/?p=934#comment-1279</guid> <description>Thanks, this is &lt;em&gt;very&lt;/em&gt; helpful.</description> <content:encoded><![CDATA[<p>Thanks, this is <em>very</em> helpful.</p> ]]></content:encoded> </item> <item><title>By: Praveen Vijayan</title><link>http://brenelz.com/blog/css-line-break-bug-screencast/comment-page-1/#comment-1280</link> <dc:creator>Praveen Vijayan</dc:creator> <pubDate>Sat, 18 Apr 2009 07:37:17 +0000</pubDate> <guid isPermaLink="false">http://www.brenelz.com/blog/?p=934#comment-1280</guid> <description>Thanks to point out this issueThis type of issue happen in ie when there is a gap between img tag and its preceding or succeeding element.eg:a white gap will show in ie between image and div. The following will eliminate this white gap.</description> <content:encoded><![CDATA[<p>Thanks to point out this issue</p><p>This type of issue happen in ie when there is a gap between img tag and its preceding or succeeding element.</p><p>eg:</p><p>a white gap will show in ie between image and div. The following will eliminate this white gap.</p> ]]></content:encoded> </item> <item><title>By: Gopal Raju</title><link>http://brenelz.com/blog/css-line-break-bug-screencast/comment-page-1/#comment-1281</link> <dc:creator>Gopal Raju</dc:creator> <pubDate>Sat, 18 Apr 2009 04:31:14 +0000</pubDate> <guid isPermaLink="false">http://www.brenelz.com/blog/?p=934#comment-1281</guid> <description>Nice Solution!Gopal Raju productivedreams.com twitter.com/gopalraju</description> <content:encoded><![CDATA[<p>Nice Solution!</p><p>Gopal Raju<br /> productivedreams.com<br /> twitter.com/gopalraju</p> ]]></content:encoded> </item> </channel> </rss>
<!-- Performance optimized by W3 Total Cache. Learn more: http://www.w3-edge.com/wordpress-plugins/

Minified using disk: basic
Page Caching using disk: enhanced (User agent is rejected)
Database Caching 26/44 queries in 0.009 seconds using disk: basic
Object Caching 670/671 objects using disk: basic

Served from: brenelz.com @ 2012-02-09 04:42:38 -->
