<?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>Pivotal Labs &#187; Alex Lobascio</title>
	<atom:link href="http://pivotallabs.com/author/lobascio/feed/" rel="self" type="application/rss+xml" />
	<link>http://pivotallabs.com</link>
	<description>Agility Developed</description>
	<lastBuildDate>Fri, 17 May 2013 20:10:59 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.5.1</generator>
		<item>
		<title>[Standup][SF] 3/28/2012</title>
		<link>http://pivotallabs.com/standup-sf-3-28-2012/</link>
		<comments>http://pivotallabs.com/standup-sf-3-28-2012/#comments</comments>
		<pubDate>Wed, 28 Mar 2012 17:12:00 +0000</pubDate>
		<dc:creator>Alex Lobascio</dc:creator>
				<category><![CDATA[Standup]]></category>

		<guid isPermaLink="false">http://pivotallabs.com/standup-sf-3-28-2012/</guid>
		<description><![CDATA[<p><h2>Interesting</h2>

<p>A project is moving from their initial layouts to Bootstrap. They have quite a few class name conflicts in their css, so in order to isolate the new Bootstrap styles to specific elements, they added the Bootstrap styles to their own &#40;in SASS&#41; under a .bootstrap namespace, and are nesting any new elements under divs with a class of .bootstrap, and now everything is pretty again.</p>

<p>Nesting in this way &#40;rather than namespacing all of the preexisting css&#41; ensures that no Bootstrap styling leaks into pre-existing elements, but means that occasionally a pre-Bootstrap style will leak into the new namespaced elements due to higher selector specificity.</p> <a href="http://pivotallabs.com/standup-sf-3-28-2012/">Continue reading <span class="meta-nav">&#8594;</span></a></p><p>The post <a href="http://pivotallabs.com/standup-sf-3-28-2012/">[Standup][SF] 3/28/2012</a> appeared first on <a href="http://pivotallabs.com">Pivotal Labs</a>.</p>]]></description>
				<content:encoded><![CDATA[<h2>Interesting</h2>
<p>A project is moving from their initial layouts to Bootstrap. They have quite a few class name conflicts in their css, so in order to isolate the new Bootstrap styles to specific elements, they added the Bootstrap styles to their own &#40;in SASS&#41; under a .bootstrap namespace, and are nesting any new elements under divs with a class of .bootstrap, and now everything is pretty again.</p>
<p>Nesting in this way &#40;rather than namespacing all of the preexisting css&#41; ensures that no Bootstrap styling leaks into pre-existing elements, but means that occasionally a pre-Bootstrap style will leak into the new namespaced elements due to higher selector specificity.</p>
<p>The post <a href="http://pivotallabs.com/standup-sf-3-28-2012/">[Standup][SF] 3/28/2012</a> appeared first on <a href="http://pivotallabs.com">Pivotal Labs</a>.</p>]]></content:encoded>
			<wfw:commentRss>http://pivotallabs.com/standup-sf-3-28-2012/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Standup 12/19/2011: Fun with IE8</title>
		<link>http://pivotallabs.com/standup-12-19-2011-fun-with-ie8/</link>
		<comments>http://pivotallabs.com/standup-12-19-2011-fun-with-ie8/#comments</comments>
		<pubDate>Mon, 19 Dec 2011 16:05:00 +0000</pubDate>
		<dc:creator>Alex Lobascio</dc:creator>
				<category><![CDATA[Standup]]></category>
		<category><![CDATA[agile]]></category>

		<guid isPermaLink="false">http://pivotallabs.com/standup-12-19-2011-fun-with-ie8/</guid>
		<description><![CDATA[<p><h2>Help</h2>

<p>JQuery FileUpload + IE8 = Access Denied when trying to upload a file. Turns out the team was styling the file input button to hide the actual file input, but had accidentally given it a width of 1px. The file chooser was working on other browsers because a "choose" event was wired to the actually visible button, which IE couldn't deal with.</p>

<h2>Interesting</h2>

<p>IE8 Caching: IE8 will cache responses with 200 response codes. This can be a problem if your user hits a login-required page, gets a 200 on the response to that, logs in, and attempts to revisit the page. Properly setting cache control headers &#40;which Rails does by default&#41; should fix it.</p>

<p>The Heroku Cedar stack uses Ruby 1.9.2.p290. Just sayin'</p> <a href="http://pivotallabs.com/standup-12-19-2011-fun-with-ie8/">Continue reading <span class="meta-nav">&#8594;</span></a></p><p>The post <a href="http://pivotallabs.com/standup-12-19-2011-fun-with-ie8/">Standup 12/19/2011: Fun with IE8</a> appeared first on <a href="http://pivotallabs.com">Pivotal Labs</a>.</p>]]></description>
				<content:encoded><![CDATA[<h2>Help</h2>
<p>JQuery FileUpload + IE8 = Access Denied when trying to upload a file. Turns out the team was styling the file input button to hide the actual file input, but had accidentally given it a width of 1px. The file chooser was working on other browsers because a &#8220;choose&#8221; event was wired to the actually visible button, which IE couldn&#8217;t deal with.</p>
<h2>Interesting</h2>
<p>IE8 Caching: IE8 will cache responses with 200 response codes. This can be a problem if your user hits a login-required page, gets a 200 on the response to that, logs in, and attempts to revisit the page. Properly setting cache control headers &#40;which Rails does by default&#41; should fix it.</p>
<p>The Heroku Cedar stack uses Ruby 1.9.2.p290. Just sayin&#8217;</p>
<p>IE was giving us &#8220;Access is Denied&#8221; when using the jQuery fileupload plugin and trying to upload a file.  We were styling the file input button in the usual way of hiding the actual file input, but at some point somebody had set the width to 1px.  The reason the file picker was still working was somebody had wired a &#8220;choose&#8221; event to the visible button, which worked in all browsers except IE. </p>
<p>The post <a href="http://pivotallabs.com/standup-12-19-2011-fun-with-ie8/">Standup 12/19/2011: Fun with IE8</a> appeared first on <a href="http://pivotallabs.com">Pivotal Labs</a>.</p>]]></content:encoded>
			<wfw:commentRss>http://pivotallabs.com/standup-12-19-2011-fun-with-ie8/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Standup 7/15/2011</title>
		<link>http://pivotallabs.com/standup-7-15-2011/</link>
		<comments>http://pivotallabs.com/standup-7-15-2011/#comments</comments>
		<pubDate>Fri, 15 Jul 2011 21:52:00 +0000</pubDate>
		<dc:creator>Alex Lobascio</dc:creator>
				<category><![CDATA[Standup]]></category>
		<category><![CDATA[agile]]></category>

		<guid isPermaLink="false">http://pivotallabs.com/standup-7-15-2011/</guid>
		<description><![CDATA[<p><h2>Help!</h2>

<p>Does anyone know of a library or canonical source for three-digit airport codes?
Edit: Pivots came up with http://www.airportcodes.org/ and http://www.halfgaar.net/localized-world-airport-codes</p>

<h2>Interesting:</h2>

<p>Ruby 1.9.2.p290 was released last night. Looks like it fixed some YML-related problems.</p>

<p>A pair was having problems with Sass on their production environment on Heroku this last week. They've discovered a bug and created a sample project/bug report for it, which will be linked here when it's posted.</p> <a href="http://pivotallabs.com/standup-7-15-2011/">Continue reading <span class="meta-nav">&#8594;</span></a></p><p>The post <a href="http://pivotallabs.com/standup-7-15-2011/">Standup 7/15/2011</a> appeared first on <a href="http://pivotallabs.com">Pivotal Labs</a>.</p>]]></description>
				<content:encoded><![CDATA[<h2>Help!</h2>
<p>Does anyone know of a library or canonical source for three-digit airport codes?<br />
Edit: Pivots came up with http://www.airportcodes.org/ and http://www.halfgaar.net/localized-world-airport-codes</p>
<h2>Interesting:</h2>
<p>Ruby 1.9.2.p290 was released last night. Looks like it fixed some YML-related problems.</p>
<p>A pair was having problems with Sass on their production environment on Heroku this last week. They&#8217;ve discovered a bug and created a sample project/bug report for it, which will be linked here when it&#8217;s posted.</p>
<p>The post <a href="http://pivotallabs.com/standup-7-15-2011/">Standup 7/15/2011</a> appeared first on <a href="http://pivotallabs.com">Pivotal Labs</a>.</p>]]></content:encoded>
			<wfw:commentRss>http://pivotallabs.com/standup-7-15-2011/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Standup 7/13/2011</title>
		<link>http://pivotallabs.com/standup-7-13-2011/</link>
		<comments>http://pivotallabs.com/standup-7-13-2011/#comments</comments>
		<pubDate>Wed, 13 Jul 2011 20:07:00 +0000</pubDate>
		<dc:creator>Alex Lobascio</dc:creator>
				<category><![CDATA[Standup]]></category>
		<category><![CDATA[agile]]></category>

		<guid isPermaLink="false">http://pivotallabs.com/standup-7-13-2011/</guid>
		<description><![CDATA[<p><h2>Interesting:</h2>

<p>Jasmine 1.1.0.rc3 has been released!
Check it out on <a href="https://github.com/pivotal/jasmine">github</a>.</p>

<h2>Help!:</h2>

<p>One pair was having problems getting custom Devise views for the sessions controller to appear. <a href="http://stackoverflow.com/questions/5307924/devise-custom-controller-users-old-views">StackOverflow</a> suggests that when using a custom extension of a Devise controller, new views must be placed into app/views/<em>controller_name</em>/ as appropriate.</p> <a href="http://pivotallabs.com/standup-7-13-2011/">Continue reading <span class="meta-nav">&#8594;</span></a></p><p>The post <a href="http://pivotallabs.com/standup-7-13-2011/">Standup 7/13/2011</a> appeared first on <a href="http://pivotallabs.com">Pivotal Labs</a>.</p>]]></description>
				<content:encoded><![CDATA[<h2>Interesting:</h2>
<p>Jasmine 1.1.0.rc3 has been released!<br />
Check it out on <a href="https://github.com/pivotal/jasmine">github</a>.</p>
<h2>Help!:</h2>
<p>One pair was having problems getting custom Devise views for the sessions controller to appear. <a href="http://stackoverflow.com/questions/5307924/devise-custom-controller-users-old-views">StackOverflow</a> suggests that when using a custom extension of a Devise controller, new views must be placed into app/views/<em>controller_name</em>/ as appropriate.</p>
<p>The post <a href="http://pivotallabs.com/standup-7-13-2011/">Standup 7/13/2011</a> appeared first on <a href="http://pivotallabs.com">Pivotal Labs</a>.</p>]]></content:encoded>
			<wfw:commentRss>http://pivotallabs.com/standup-7-13-2011/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

<!-- Performance optimized by W3 Total Cache. Learn more: http://www.w3-edge.com/wordpress-plugins/

Minified using disk: basic (Feed is rejected)
Page Caching using apc
Database Caching using apc
Object Caching 636/678 objects using apc

 Served from: pivotallabs.com @ 2013-05-18 11:10:13 by W3 Total Cache -->