<?xml version="1.0" encoding="utf-8"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title>Gabriel Weinberg's Blog - Latest Comments in A Harsh CSS Environment for Testing Widgets</title><link>http://yegg.disqus.com/</link><description>Startups &amp; stuff...</description><atom:link href="https://yegg.disqus.com/a_harsh_css_environment_for_testing_widgets/latest.rss" rel="self"></atom:link><language>en</language><lastBuildDate>Tue, 09 Jun 2009 07:38:44 -0000</lastBuildDate><item><title>Re: A Harsh CSS Environment for Testing Widgets</title><link>http://www.gabrielweinberg.com/blog/2009/06/a-harsh-css-environment-for-testing-widgets.html#comment-10647410</link><description>&lt;p&gt;What do you mean by CSS Reset?  Something like &lt;a href="http://developer.yahoo.com/yui/reset/" rel="nofollow noopener" target="_blank" title="http://developer.yahoo.com/yui/reset/"&gt;http://developer.yahoo.com/...&lt;/a&gt; ?.  That is effectively what #armor is.  The YUI reset does not reset enough things.  Try it!&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Gabriel Weinberg</dc:creator><pubDate>Tue, 09 Jun 2009 07:38:44 -0000</pubDate></item><item><title>Re: A Harsh CSS Environment for Testing Widgets</title><link>http://www.gabrielweinberg.com/blog/2009/06/a-harsh-css-environment-for-testing-widgets.html#comment-10643308</link><description>&lt;p&gt;Does a properly scoped CSS Reset not do the trick in a harsh environment?&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Peter Goodman</dc:creator><pubDate>Tue, 09 Jun 2009 02:00:13 -0000</pubDate></item><item><title>Re: A Harsh CSS Environment for Testing Widgets</title><link>http://www.gabrielweinberg.com/blog/2009/06/a-harsh-css-environment-for-testing-widgets.html#comment-10618369</link><description>&lt;p&gt;I just used this for the Scribnia (&lt;a href="http://scribnia.com" rel="nofollow noopener" target="_blank" title="http://scribnia.com"&gt;http://scribnia.com&lt;/a&gt;) widget.  Extremely helpful--I modified the armor a little bit and then stuck it right into our widget's code. Thanks a lot Gabriel.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">jackgretz</dc:creator><pubDate>Mon, 08 Jun 2009 12:59:05 -0000</pubDate></item><item><title>Re: A Harsh CSS Environment for Testing Widgets</title><link>http://www.gabrielweinberg.com/blog/2009/06/a-harsh-css-environment-for-testing-widgets.html#comment-10594907</link><description>&lt;p&gt;Np.  I love the Skirbit idea as I continually have writer's block.  I actually added it to the Duck Duck Go Blog today as well (&lt;a href="http://duckduckgo.com/blog/)" rel="nofollow noopener" target="_blank" title="http://duckduckgo.com/blog/)"&gt;http://duckduckgo.com/blog/)&lt;/a&gt;, where I have even more writer's block! I hope people give me some good ideas soon...&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Gabriel Weinberg</dc:creator><pubDate>Sun, 07 Jun 2009 16:44:52 -0000</pubDate></item><item><title>Re: A Harsh CSS Environment for Testing Widgets</title><link>http://www.gabrielweinberg.com/blog/2009/06/a-harsh-css-environment-for-testing-widgets.html#comment-10594863</link><description>&lt;p&gt;Not if they want a static link that counts for SEO purposes :).&lt;/p&gt;&lt;p&gt;Wrt to injecting CSS, you can do it via JS by creating a link element and appending it to the head tag. It has its issues (&lt;a href="http://wiki.fluidproject.org/display/fluid/Methods+and+Limitations+for+dynamically+changing+styles)" rel="nofollow noopener" target="_blank" title="http://wiki.fluidproject.org/display/fluid/Methods+and+Limitations+for+dynamically+changing+styles)"&gt;http://wiki.fluidproject.or...&lt;/a&gt; but it is the cleanest in terms of copy and paste for the user, i.e. they can just copy and paste a JS line.&lt;/p&gt;&lt;p&gt;At the moment I'm leaning towards putting it all inline, however.  It is the safest way to make sure it renders correctly, and you can avoid JS altogether if you don't need it.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Gabriel Weinberg</dc:creator><pubDate>Sun, 07 Jun 2009 16:42:07 -0000</pubDate></item><item><title>Re: A Harsh CSS Environment for Testing Widgets</title><link>http://www.gabrielweinberg.com/blog/2009/06/a-harsh-css-environment-for-testing-widgets.html#comment-10594422</link><description>&lt;p&gt;Thanks for this! I figure I'll need to run Skribit's widgets through this and tweak as necessary. (oh and thanks for using Skribit!)&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Paul Stamatiou</dc:creator><pubDate>Sun, 07 Jun 2009 16:18:43 -0000</pubDate></item><item><title>Re: A Harsh CSS Environment for Testing Widgets</title><link>http://www.gabrielweinberg.com/blog/2009/06/a-harsh-css-environment-for-testing-widgets.html#comment-10593924</link><description>&lt;p&gt;I guess the truly paranoid can use iframes, right?&lt;/p&gt;&lt;p&gt;One question: what is the most reliable way you've found for injecting CSS?&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Jed Schmidt</dc:creator><pubDate>Sun, 07 Jun 2009 15:48:37 -0000</pubDate></item><item><title>Re: A Harsh CSS Environment for Testing Widgets</title><link>http://www.gabrielweinberg.com/blog/2009/06/a-harsh-css-environment-for-testing-widgets.html#comment-10593523</link><description>&lt;p&gt;Refresh your screen--I forgot the /blog/ part at first and then edited the comment :)&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Gabriel Weinberg</dc:creator><pubDate>Sun, 07 Jun 2009 15:26:44 -0000</pubDate></item><item><title>Re: A Harsh CSS Environment for Testing Widgets</title><link>http://www.gabrielweinberg.com/blog/2009/06/a-harsh-css-environment-for-testing-widgets.html#comment-10593509</link><description>&lt;p&gt;Thanks for the quick response, but I'm getting 404s for both URLs.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">scribu</dc:creator><pubDate>Sun, 07 Jun 2009 15:25:11 -0000</pubDate></item><item><title>Re: A Harsh CSS Environment for Testing Widgets</title><link>http://www.gabrielweinberg.com/blog/2009/06/a-harsh-css-environment-for-testing-widgets.html#comment-10593380</link><description>&lt;p&gt;Yeah, in the widget I'm working on, I reset 'display' to inline after #armor for inline elements.  You're probably right that it is a bit too paranoid though.  However, I suppose the bloat in this case is greatly reduced when people use gzip (increasingly so) since it will be gzipped away.&lt;/p&gt;&lt;p&gt;As for the modern properties, they should probably be added, at least the ones that often get used.  I suppose if you added *all* of them you'd get some serious bloat!&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Gabriel Weinberg</dc:creator><pubDate>Sun, 07 Jun 2009 15:17:47 -0000</pubDate></item><item><title>Re: A Harsh CSS Environment for Testing Widgets</title><link>http://www.gabrielweinberg.com/blog/2009/06/a-harsh-css-environment-for-testing-widgets.html#comment-10593321</link><description>&lt;p&gt;I removed the 'content' property from #harsh and the examples because it was messing up images and I'm not sure how to prevent that within #armor.  Any suggestions are appreciated.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Gabriel Weinberg</dc:creator><pubDate>Sun, 07 Jun 2009 15:13:32 -0000</pubDate></item><item><title>Re: A Harsh CSS Environment for Testing Widgets</title><link>http://www.gabrielweinberg.com/blog/2009/06/a-harsh-css-environment-for-testing-widgets.html#comment-10593282</link><description>&lt;p&gt;Here you go: &lt;a href="http://www.gabrielweinberg.com/blog/armor-min.css" rel="nofollow noopener" target="_blank" title="http://www.gabrielweinberg.com/blog/armor-min.css"&gt;http://www.gabrielweinberg....&lt;/a&gt; &amp;amp; &lt;a href="http://www.gabrielweinberg.com/blog/harsh-min.css" rel="nofollow noopener" target="_blank" title="http://www.gabrielweinberg.com/blog/harsh-min.css"&gt;http://www.gabrielweinberg....&lt;/a&gt;&lt;/p&gt;&lt;p&gt;&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Gabriel Weinberg</dc:creator><pubDate>Sun, 07 Jun 2009 15:11:04 -0000</pubDate></item><item><title>Re: A Harsh CSS Environment for Testing Widgets</title><link>http://www.gabrielweinberg.com/blog/2009/06/a-harsh-css-environment-for-testing-widgets.html#comment-10593242</link><description>&lt;p&gt;This is a cool idea: a CSS Reset for widgets.&lt;/p&gt;&lt;p&gt;I'd imagine you'll need to protect against many others for more modern CSS (such as-border-radius, -moz-border-radius, and -webkit-border-radius). Also, any inline elements (span, em, strong, etc.) will display as block within the armor. Solving proliferating styles and inline/block elements will probably add more bloat than value, though.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Jed Schmidt</dc:creator><pubDate>Sun, 07 Jun 2009 15:09:31 -0000</pubDate></item><item><title>Re: A Harsh CSS Environment for Testing Widgets</title><link>http://www.gabrielweinberg.com/blog/2009/06/a-harsh-css-environment-for-testing-widgets.html#comment-10592913</link><description>&lt;p&gt;Pretty cool concept. A minified version of #harsh and #armor would be handy.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">scribu</dc:creator><pubDate>Sun, 07 Jun 2009 14:53:21 -0000</pubDate></item></channel></rss>