<?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>chrome Archives - Pietari Heino&#039;s personal website</title>
	<atom:link href="https://www.extreg.com/blog/tag/chrome/feed/" rel="self" type="application/rss+xml" />
	<link>https://www.extreg.com</link>
	<description></description>
	<lastBuildDate>Mon, 21 Nov 2016 04:37:29 +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>
		<item>
		<title>Chrome password manager is slow [fixed]</title>
		<link>https://www.extreg.com/blog/2016/07/chrome-password-manager-is-slow/</link>
					<comments>https://www.extreg.com/blog/2016/07/chrome-password-manager-is-slow/#comments</comments>
		
		<dc:creator><![CDATA[Pietari]]></dc:creator>
		<pubDate>Sat, 02 Jul 2016 10:51:00 +0000</pubDate>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[chrome]]></category>
		<category><![CDATA[chrome password manager]]></category>
		<guid isPermaLink="false">https://extreg.com/?p=60</guid>

					<description><![CDATA[<p>I don&#8217;t really know the reason, but the integrated password manager in Chrome has become awfully and absurdly slow for me. It usually takes multiple seconds to actually realize that the browser has loaded a page with a login field and that it even holds some credentials for it. And I am not exaggerating this: it really ... <span class="more"><a class="more-link" href="https://www.extreg.com/blog/2016/07/chrome-password-manager-is-slow/">[Read more...]</a></span></p>
<p>The post <a rel="nofollow" href="https://www.extreg.com/blog/2016/07/chrome-password-manager-is-slow/">Chrome password manager is slow [fixed]</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>I don&#8217;t really know the reason, but the integrated password manager in Chrome has become awfully and absurdly slow for me. It usually takes multiple seconds to actually realize that the browser has loaded a page with a login field and that it even holds some credentials for it. And I am not exaggerating this: it really does take from 4 to 10 seconds to fill in my username and password, and this is unforgivable. It makes the user experience horrible. You load the page, you see ~ all JS has been executed, everything is in its place and nicely settled, but wait&#8230; another couple of seconds &#8217;til you can login.</p>
<p><strong>UPDATE! Please see the discussions <a href="https://bugs.chromium.org/p/chromium/issues/detail?id=651049">here</a> and <a href="https://bugs.chromium.org/p/chromium/issues/detail?id=660357">here</a>.</strong></p>
<p>UPDATE #2! I believe the Chrome team has implemented a fix for this since the now-beta version 55.x.x.x brings up the password management window instantly and doesn&#8217;t hang.</p>
<p>I have no idea how many passwords there are in my Chrome password manager but it goes without saying that might have something to do with the slowness. Of course, one might say, an engineering error or a place to optimize the software, since no matter how many pairs of credentials I have stored there, it should be fast and not make the user sit and wait (and really, how many can you even have so that it would realistically be OK to take so long to check them?).</p>
<p>I&#8217;m planning to do some testing and go through the db to see if the waiting time cuts off and file a bug report if needed. Huh.</p>
<p>The post <a rel="nofollow" href="https://www.extreg.com/blog/2016/07/chrome-password-manager-is-slow/">Chrome password manager is slow [fixed]</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/07/chrome-password-manager-is-slow/feed/</wfw:commentRss>
			<slash:comments>5</slash:comments>
		
		
		<post-id xmlns="com-wordpress:feed-additions:1">60</post-id>	</item>
	</channel>
</rss>
