<?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/"
	
	xmlns:georss="http://www.georss.org/georss"
	xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#"
	>

<channel>
	<title>critical css Archives - Pietari Heino&#039;s personal website</title>
	<atom:link href="https://www.extreg.com/blog/tag/critical-css/feed/" rel="self" type="application/rss+xml" />
	<link>https://www.extreg.com</link>
	<description></description>
	<lastBuildDate>Fri, 11 Nov 2016 23:40:40 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=5.6.7</generator>
<site xmlns="com-wordpress:feed-additions:1">99365322</site>	<item>
		<title>CSS coverage, edit local files, inline breakpoints&#8230; [Chrome DevTools]</title>
		<link>https://www.extreg.com/blog/2016/11/css-coverage-edit-local-files-inline-breakpoints-chrome-devtools/</link>
					<comments>https://www.extreg.com/blog/2016/11/css-coverage-edit-local-files-inline-breakpoints-chrome-devtools/#respond</comments>
		
		<dc:creator><![CDATA[Pietari]]></dc:creator>
		<pubDate>Fri, 11 Nov 2016 23:38:36 +0000</pubDate>
				<category><![CDATA[random]]></category>
		<category><![CDATA[chrome]]></category>
		<category><![CDATA[chrome dev tools]]></category>
		<category><![CDATA[critical css]]></category>
		<guid isPermaLink="false">https://extreg.com/?p=98</guid>

					<description><![CDATA[<p>The Chrome team has added a bunch of very nice and shiny features to the Chrome DevTools. They should be available in the Canary branch right now and reach beta and stable at later dates. Unfortunately there&#8217;s no Canary for Linux so I&#8217;m not able to test these yet, blargh. Best new features in my ... <span class="more"><a class="more-link" href="https://www.extreg.com/blog/2016/11/css-coverage-edit-local-files-inline-breakpoints-chrome-devtools/">[Read more...]</a></span></p>
<p>The post <a rel="nofollow" href="https://www.extreg.com/blog/2016/11/css-coverage-edit-local-files-inline-breakpoints-chrome-devtools/">CSS coverage, edit local files, inline breakpoints&#8230; [Chrome DevTools]</a> appeared first on <a rel="nofollow" href="https://www.extreg.com">Pietari Heino&#039;s personal website</a>.</p>
]]></description>
										<content:encoded><![CDATA[<p>The Chrome team has added a bunch of very nice and shiny features to the Chrome DevTools. They should be available in the Canary branch right now and reach beta and stable at later dates. Unfortunately there&#8217;s no Canary for Linux so I&#8217;m not able to test these yet, blargh.</p>
<p>Best new features in my opinion:</p>
<ul>
<li>CSS coverage by recording a timeline</li>
<li>Persistent file editing via DevTools</li>
<li>Automatic local project folder mapping</li>
<li>Inline breakpoints</li>
<li>Web and Node debugging at the same time</li>
</ul>
<p>There are other additions as well. Check out this <a href="https://www.youtube.com/watch?v=HF1luRD4Qmk">Debugging the Web</a> video from Chrome Dev Summit 2016 to learn more. There&#8217;s also a nice little GIF showing how the CSS coverage works over at <a href="https://umaar.com/dev-tips/121-css-coverage/">umaar.com</a>.</p>
<p>The post <a rel="nofollow" href="https://www.extreg.com/blog/2016/11/css-coverage-edit-local-files-inline-breakpoints-chrome-devtools/">CSS coverage, edit local files, inline breakpoints&#8230; [Chrome DevTools]</a> appeared first on <a rel="nofollow" href="https://www.extreg.com">Pietari Heino&#039;s personal website</a>.</p>
]]></content:encoded>
					
					<wfw:commentRss>https://www.extreg.com/blog/2016/11/css-coverage-edit-local-files-inline-breakpoints-chrome-devtools/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
		<post-id xmlns="com-wordpress:feed-additions:1">98</post-id>	</item>
	</channel>
</rss>
