<?xml version="1.0" encoding="UTF-8"?> <rss
version="2.0"
xmlns:content="http://purl.org/rss/1.0/modules/content/"
xmlns:wfw="http://wellformedweb.org/CommentAPI/"
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/"
xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
> <channel><title>Project 2061 Techlog &#187; css</title> <atom:link href="http://techlog.p2061.org/tag/css/feed/" rel="self" type="application/rss+xml" /><link>http://techlog.p2061.org</link> <description>Blogging from Project 2061 technology group</description> <lastBuildDate>Tue, 06 Sep 2011 14:49:39 +0000</lastBuildDate> <language>en</language> <sy:updatePeriod>hourly</sy:updatePeriod> <sy:updateFrequency>1</sy:updateFrequency> <generator>http://wordpress.org/?v=3.3.1</generator> <item><title>Updates for IE8</title><link>http://techlog.p2061.org/2009/02/20/updates-for-ie8/</link> <comments>http://techlog.p2061.org/2009/02/20/updates-for-ie8/#comments</comments> <pubDate>Fri, 20 Feb 2009 21:00:43 +0000</pubDate> <dc:creator>bsweeney</dc:creator> <category><![CDATA[Web Development]]></category> <category><![CDATA[css]]></category> <category><![CDATA[ie]]></category> <category><![CDATA[javascript]]></category> <guid
isPermaLink="false">http://techlog.p2061.org/?p=211</guid> <description><![CDATA[With the release of IE8 getting closer I took a moment to check out our web site and Benchmarks Online in the new browser. As I suspected, the incompatibilities on our web site were of the same ilk as when IE7 was released and required minor updates. The updates to Benchmarks were also fairly minor, [...]]]></description> <content:encoded><![CDATA[<p>With the release of IE8 getting closer I took a moment to check out our web site and <em>Benchmarks Online</em> in the new browser. As I suspected, the incompatibilities on our web site were of the same ilk as when IE7 was released and required minor updates. The updates to <em>Benchmarks</em> were also fairly minor, though did require a bit of effort to track down. Luckily IE8 includes developer tools right in the browser, making debugging web content much easier.</p><p>While I was at it, I decided to see how the JS+CSS was working in Safari (latest version on Windows and Mac) and Opera (latest versions on Windows). There were some minor issues with these browsers that I fixed as well. Quickly, Safari and Opera both were having trouble displaying the bullets in my ordered list when the pseudo multi-column-styling was applied. The odd thing is that the numbers were there, just not visible until an element was forced on top of them.</p><p>Finally, I decided to update the multi-column list code on the web site to that used in Benchmarks (which is more robust). I did run across one problem in the update that I may have to investigate further. Essentially, the script was not correctly positioning the second+ columns if a margin was specified on the container OL/UL.</p> ]]></content:encoded> <wfw:commentRss>http://techlog.p2061.org/2009/02/20/updates-for-ie8/feed/</wfw:commentRss> <slash:comments>0</slash:comments> </item> <item><title>Your float is showing</title><link>http://techlog.p2061.org/2008/11/21/your-float-is-showing/</link> <comments>http://techlog.p2061.org/2008/11/21/your-float-is-showing/#comments</comments> <pubDate>Fri, 21 Nov 2008 20:27:37 +0000</pubDate> <dc:creator>bsweeney</dc:creator> <category><![CDATA[Web Development]]></category> <category><![CDATA[bugs]]></category> <category><![CDATA[css]]></category> <category><![CDATA[quirks]]></category> <category><![CDATA[style]]></category> <guid
isPermaLink="false">http://techlog.p2061.org/?p=145</guid> <description><![CDATA[Float styling is a useful aspect of CSS &#8230; until it&#8217;s not. When a floated element occurs inside a container and you want it to be wholly in that container you have to resort to hacks to do so. Or do you? Never content to assume that a question has been resolved, I decided to [...]]]></description> <content:encoded><![CDATA[<p>Float styling is a useful aspect of CSS &#8230; until it&#8217;s not. When a floated element occurs inside a container and you want it to be wholly in that container you have to resort to hacks to do so. Or do you? Never content to assume that a question has been resolved, I decided to see if anyone had come up with a new method of clearing a float. Lo and behold a solution has emerged, and the solution is so simple as to defy logic: apply <code>overflow: auto</code> to the container element. I&#8217;ll leave the full explanation (with examples, alternatives, and warnings) to the experts.</p><ul><li><a
href="http://www.sitepoint.com/simple-clearing-of-floats/">SitePoint: Simple Clearing of Floats</a></li><li><a
href="http://www.quirksmode.org/css/clearing.html">QuirksMode: Clearing Floats</a></li><li><a
href="http://www.mezzoblue.com/archives/2005/03/03/clearance/">mezzoblue: Clearance</a></li></ul><p>Of course, there can be advantages to the default float rendering. Most notably I found it useful for creating some nice formatting around blockquotes, such as in our <a
href="http://www.project2061.org/publications/textbook/hsbio/report/reports/biology/sfContent.htm">textbook analysis report</a>.</p> ]]></content:encoded> <wfw:commentRss>http://techlog.p2061.org/2008/11/21/your-float-is-showing/feed/</wfw:commentRss> <slash:comments>0</slash:comments> </item> <item><title>CSS Quirk: opacity</title><link>http://techlog.p2061.org/2008/10/10/css-quirk-opacity/</link> <comments>http://techlog.p2061.org/2008/10/10/css-quirk-opacity/#comments</comments> <pubDate>Fri, 10 Oct 2008 19:50:49 +0000</pubDate> <dc:creator>bsweeney</dc:creator> <category><![CDATA[Adobe Illustrator]]></category> <category><![CDATA[Web Development]]></category> <category><![CDATA[css]]></category> <category><![CDATA[style]]></category> <guid
isPermaLink="false">http://techlog.p2061.org/?p=108</guid> <description><![CDATA[Elements with opacity styling are stacked independent of their containing object. As a result, any positioned elements that do not have a z-index declaration and that appear in the HTML code prior to an opacity-styled element will appear underneath the opacity-styled element (see example). This is the defined behavior in the CSS specification, though currently [...]]]></description> <content:encoded><![CDATA[<p>Elements with opacity styling are stacked independent of their containing object. As a result, any positioned elements that do not have a z-index declaration and that appear in the HTML code prior to an opacity-styled element will appear underneath the opacity-styled element (<a
href="http://techlog.p2061.org/wp-content/uploads/2008/10/opacity.htm">see example</a>). This is the defined behavior in the CSS specification, though currently only gecko- and WebKit-based browsers (Firefox, Safari, Chrome) exhibit the &#8220;quirk&#8221; in question. From the CSS3 Working Draft:</p><blockquote
cite="http://www.w3.org/TR/css3-color/#transparency"><p>&#8230; implementations must create a new stacking context for any element with opacity less than 1.</p><p><a
href="http://www.w3.org/TR/css3-color/#transparency">CSS Color Module Level 3: Working Draft 21 July 2008</a></p></blockquote> ]]></content:encoded> <wfw:commentRss>http://techlog.p2061.org/2008/10/10/css-quirk-opacity/feed/</wfw:commentRss> <slash:comments>0</slash:comments> </item> </channel> </rss>
