<?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 for @drublic</title>
	<atom:link href="http://drublic.de/blog/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://drublic.de/blog</link>
	<description>A Cutting Edge Webdesign Blog</description>
	<lastBuildDate>Tue, 21 Feb 2012 09:09:32 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>Comment on Responsive Media by Sebastian</title>
		<link>http://drublic.de/blog/responsive-media/#comment-266</link>
		<dc:creator>Sebastian</dc:creator>
		<pubDate>Tue, 21 Feb 2012 09:09:32 +0000</pubDate>
		<guid isPermaLink="false">http://drublic.de/blog/?p=557#comment-266</guid>
		<description>&lt;em&gt;&lt;/em&gt;Addition to my upper response:* You have to apply fixes for IE8- because no media queries...</description>
		<content:encoded><![CDATA[<p><em></em>Addition to my upper response:* You have to apply fixes for IE8- because no media queries&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Responsive Media by Sebastian</title>
		<link>http://drublic.de/blog/responsive-media/#comment-265</link>
		<dc:creator>Sebastian</dc:creator>
		<pubDate>Tue, 21 Feb 2012 08:46:38 +0000</pubDate>
		<guid isPermaLink="false">http://drublic.de/blog/?p=557#comment-265</guid>
		<description>What do you think about using background-image? Depending on the viewport you (media-)query different versions of the image. This would solve the problem with the mobile version. Which is not loading the image at all. Plus: No need for JS.

The down side is obviously that you can not have a perfeclty scaled image. E.g.:
&lt;code&gt;height: auto;&lt;/code&gt;
&lt;code&gt;max-width: 100%;&lt;/code&gt;
So this would only work if you have a fixed grid, in which you can place the image.</description>
		<content:encoded><![CDATA[<p>What do you think about using background-image? Depending on the viewport you (media-)query different versions of the image. This would solve the problem with the mobile version. Which is not loading the image at all. Plus: No need for JS.</p>
<p>The down side is obviously that you can not have a perfeclty scaled image. E.g.:<br />
<code>height: auto;</code><br />
<code>max-width: 100%;</code><br />
So this would only work if you have a fixed grid, in which you can place the image.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Responsive Media by Sebastian</title>
		<link>http://drublic.de/blog/responsive-media/#comment-264</link>
		<dc:creator>Sebastian</dc:creator>
		<pubDate>Mon, 20 Feb 2012 20:43:39 +0000</pubDate>
		<guid isPermaLink="false">http://drublic.de/blog/?p=557#comment-264</guid>
		<description>Yeah an update would be nice! :)

The thing I struggle is that the DOM-node should not be created, otherwhise the image is already requested (500KB in my case, not really something you want to load with a smart phone).

This also means that I can not load all JS after the HTML content, b/c the script has to be executed on load. Which means I have to write REAL JavaScript not JQuery! :-o</description>
		<content:encoded><![CDATA[<p>Yeah an update would be nice! :)</p>
<p>The thing I struggle is that the DOM-node should not be created, otherwhise the image is already requested (500KB in my case, not really something you want to load with a smart phone).</p>
<p>This also means that I can not load all JS after the HTML content, b/c the script has to be executed on load. Which means I have to write REAL JavaScript not JQuery! :-o</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on The CSS Hierarchies Module Level 3 by Lea Verou</title>
		<link>http://drublic.de/blog/the-css-hierarchies-module-level-3/#comment-261</link>
		<dc:creator>Lea Verou</dc:creator>
		<pubDate>Fri, 17 Feb 2012 15:43:46 +0000</pubDate>
		<guid isPermaLink="false">http://drublic.de/blog/?p=771#comment-261</guid>
		<description>There&#039;s another mailing list for this, public-css-testsuite IIRC.

I&#039;m not sure what the policy is for modules at such an early stage, but you could give it a shot, what&#039;s the worst that could happen? ;)

Also, I think their tests need a special format in their markup, you can read about it here (along with more details): http://wiki.csswg.org/test Or maybe you could just submit it and have someone else adapt it?

(I&#039;ve personally haven&#039;t contributed any tests yet, so take any advice from me with a grain of salt)</description>
		<content:encoded><![CDATA[<p>There&#8217;s another mailing list for this, public-css-testsuite IIRC.</p>
<p>I&#8217;m not sure what the policy is for modules at such an early stage, but you could give it a shot, what&#8217;s the worst that could happen? ;)</p>
<p>Also, I think their tests need a special format in their markup, you can read about it here (along with more details): <a href="http://wiki.csswg.org/test" rel="nofollow">http://wiki.csswg.org/test</a> Or maybe you could just submit it and have someone else adapt it?</p>
<p>(I&#8217;ve personally haven&#8217;t contributed any tests yet, so take any advice from me with a grain of salt)</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on The CSS Hierarchies Module Level 3 by Hans Christian</title>
		<link>http://drublic.de/blog/the-css-hierarchies-module-level-3/#comment-260</link>
		<dc:creator>Hans Christian</dc:creator>
		<pubDate>Fri, 17 Feb 2012 15:38:53 +0000</pubDate>
		<guid isPermaLink="false">http://drublic.de/blog/?p=771#comment-260</guid>
		<description>Lea,
thanks for your feedback.

That&#039;s true representing a &quot;success&quot;-state with yellow isn&#039;t what you call common. I&#039;ve changed both examples according to your suggestion. &lt;a href=&quot;http://dabblet.com/gist/1854033&quot; rel=&quot;nofollow&quot;&gt;Here&#039;s&lt;/a&gt; the one for the CSS Hierarchies Module.

Where is the right place to submit such a test? On the mailing-list? I&#039;ve no experience with this. :)</description>
		<content:encoded><![CDATA[<p>Lea,<br />
thanks for your feedback.</p>
<p>That&#8217;s true representing a &#8220;success&#8221;-state with yellow isn&#8217;t what you call common. I&#8217;ve changed both examples according to your suggestion. <a href="http://dabblet.com/gist/1854033" rel="nofollow">Here&#8217;s</a> the one for the CSS Hierarchies Module.</p>
<p>Where is the right place to submit such a test? On the mailing-list? I&#8217;ve no experience with this. :)</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on The CSS Hierarchies Module Level 3 by Lea Verou</title>
		<link>http://drublic.de/blog/the-css-hierarchies-module-level-3/#comment-259</link>
		<dc:creator>Lea Verou</dc:creator>
		<pubDate>Fri, 17 Feb 2012 15:28:12 +0000</pubDate>
		<guid isPermaLink="false">http://drublic.de/blog/?p=771#comment-259</guid>
		<description>Hi there,

Nice article.

Regarding your dabblet, please make it like a regular test: Green on success, red if failure. You could probably craft it in such a way that the entire screen is green or red, no text or anything.
Then you could even submit it to the W3C for that module&#039;s testsuite. It&#039;s trivial, but it&#039;s something, so it may help, dunno.</description>
		<content:encoded><![CDATA[<p>Hi there,</p>
<p>Nice article.</p>
<p>Regarding your dabblet, please make it like a regular test: Green on success, red if failure. You could probably craft it in such a way that the entire screen is green or red, no text or anything.<br />
Then you could even submit it to the W3C for that module&#8217;s testsuite. It&#8217;s trivial, but it&#8217;s something, so it may help, dunno.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Dabblet Chrome App by The CSS Hierarchies Module Level 3 &#124; @drublic</title>
		<link>http://drublic.de/blog/dabblet-chrome-app/#comment-258</link>
		<dc:creator>The CSS Hierarchies Module Level 3 &#124; @drublic</dc:creator>
		<pubDate>Fri, 17 Feb 2012 14:52:39 +0000</pubDate>
		<guid isPermaLink="false">http://drublic.de/blog/?p=748#comment-258</guid>
		<description>[...] or not. caniuse.com does not provide any data for the Hierarchies Module yet. Aside: Check my Dabblet Chrome App to view all your latest dabblets if you&#8217;re a Chrome [...]</description>
		<content:encoded><![CDATA[<p>[...] or not. caniuse.com does not provide any data for the Hierarchies Module yet. Aside: Check my Dabblet Chrome App to view all your latest dabblets if you&#8217;re a Chrome [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Responsive Media by Hans Christian</title>
		<link>http://drublic.de/blog/responsive-media/#comment-257</link>
		<dc:creator>Hans Christian</dc:creator>
		<pubDate>Fri, 17 Feb 2012 10:30:33 +0000</pubDate>
		<guid isPermaLink="false">http://drublic.de/blog/?p=557#comment-257</guid>
		<description>Puh. This article definitely needs an update I guess.

However: Not showing the images on a specific screen-size can be done via &quot;media-queries&quot; in JS. Run a script on the HTML code while it&#039;s loading and remove the images. Or what might work better: Load in the images only after you&#039;ve checked the screen-size. As a non-JS-fallback you could just load the images even if they are not really needed.</description>
		<content:encoded><![CDATA[<p>Puh. This article definitely needs an update I guess.</p>
<p>However: Not showing the images on a specific screen-size can be done via &#8220;media-queries&#8221; in JS. Run a script on the HTML code while it&#8217;s loading and remove the images. Or what might work better: Load in the images only after you&#8217;ve checked the screen-size. As a non-JS-fallback you could just load the images even if they are not really needed.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Responsive Media by Sebastian</title>
		<link>http://drublic.de/blog/responsive-media/#comment-256</link>
		<dc:creator>Sebastian</dc:creator>
		<pubDate>Thu, 16 Feb 2012 18:26:54 +0000</pubDate>
		<guid isPermaLink="false">http://drublic.de/blog/?p=557#comment-256</guid>
		<description>Ha funny :D Googled for responsive images. Found Hans! Nice.

If have a question on that topic. What would you do if you have different image sizes for different screens and don&#039;t want to load the image at all if the device has &lt;480px (smart phone)</description>
		<content:encoded><![CDATA[<p>Ha funny :D Googled for responsive images. Found Hans! Nice.</p>
<p>If have a question on that topic. What would you do if you have different image sizes for different screens and don&#8217;t want to load the image at all if the device has &lt;480px (smart phone)</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Dabblet Chrome App by Hans Christian</title>
		<link>http://drublic.de/blog/dabblet-chrome-app/#comment-255</link>
		<dc:creator>Hans Christian</dc:creator>
		<pubDate>Mon, 13 Feb 2012 15:16:11 +0000</pubDate>
		<guid isPermaLink="false">http://drublic.de/blog/?p=748#comment-255</guid>
		<description>Grawl,
glad you asked ;) Just talked about a Safari Extension with Tobias about it &lt;a href=&quot;https://twitter.com/#!/tobiastom/status/169067586254942208&quot; rel=&quot;nofollow&quot;&gt;on Twitter&lt;/a&gt;.
Stay tuned. Will keep you updated on this.</description>
		<content:encoded><![CDATA[<p>Grawl,<br />
glad you asked ;) Just talked about a Safari Extension with Tobias about it <a href="https://twitter.com/#!/tobiastom/status/169067586254942208" rel="nofollow">on Twitter</a>.<br />
Stay tuned. Will keep you updated on this.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

