<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Debug on dev notes</title>
    <link>https://juhanakristianblog.netlify.app/tags/debug/</link>
    <description>Recent content in Debug on dev notes</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Fri, 25 Jun 2021 23:59:01 +0000</lastBuildDate>
    <atom:link href="https://juhanakristianblog.netlify.app/tags/debug/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Hidden gems of the Chrome DevTools, Part 2: CSS tools</title>
      <link>https://juhanakristianblog.netlify.app/posts/hidden-gems-of-the-chrome-devtools-part-2/</link>
      <pubDate>Fri, 25 Jun 2021 23:59:01 +0000</pubDate>
      <guid>https://juhanakristianblog.netlify.app/posts/hidden-gems-of-the-chrome-devtools-part-2/</guid>
      <description>&lt;p&gt;In the &lt;a href=&#34;https://juhanajauhiainen.com/posts/hidden-gems-of-the-chrome-dev-tools-part-1&#34;&gt;last article on the series&lt;/a&gt; we looked into some features on the Chrome Console API. This time we&amp;rsquo;ll see some of the tools Chrome has to offer when working with CSS and layouts.&lt;/p&gt;&#xA;&lt;h2 id=&#34;inspect-layout&#34;&gt;Inspect layout&lt;/h2&gt;&#xA;&lt;p&gt;Chrome developer tools include handy tools for inspecting and debugging grid and flexbox layouts. When we open Chrome developer tools on the &lt;code&gt;Elements&lt;/code&gt; tab, you&amp;rsquo;ll find a &lt;code&gt;Layout&lt;/code&gt; tab right next to &lt;code&gt;Styles&lt;/code&gt; and &lt;code&gt;Computed&lt;/code&gt;. Under &lt;code&gt;Layout&lt;/code&gt; we will see a listing of all the grids and all the flexbox layouts on the current page.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Hidden gems of the Chrome DevTools, Part 2: CSS tools</title>
      <link>https://juhanakristianblog.netlify.app/posts/hidden-gems-of-the-chrome-dev-tools-part-3/</link>
      <pubDate>Mon, 21 Jun 2021 09:33:01 +0000</pubDate>
      <guid>https://juhanakristianblog.netlify.app/posts/hidden-gems-of-the-chrome-dev-tools-part-3/</guid>
      <description>&lt;h2 id=&#34;accessibility-features&#34;&gt;Accessibility features&lt;/h2&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;accesibility tab&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;h2 id=&#34;debugger&#34;&gt;debugger&lt;/h2&gt;&#xA;&lt;h2 id=&#34;experimental&#34;&gt;Experimental&lt;/h2&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;font editor in styles&lt;/li&gt;&#xA;&lt;li&gt;CSS overview&lt;/li&gt;&#xA;&lt;li&gt;flex box debugging&lt;/li&gt;&#xA;&lt;li&gt;accessibility tree&lt;/li&gt;&#xA;&lt;/ul&gt;</description>
    </item>
    <item>
      <title>Hidden gems of the Chrome DevTools, Part 1: The Console API</title>
      <link>https://juhanakristianblog.netlify.app/posts/hidden-gems-of-the-chrome-dev-tools-part-1/</link>
      <pubDate>Sat, 03 Apr 2021 09:33:01 +0000</pubDate>
      <guid>https://juhanakristianblog.netlify.app/posts/hidden-gems-of-the-chrome-dev-tools-part-1/</guid>
      <description>&lt;p&gt;Debugging, or finding the reason why your code doesn&amp;rsquo;t work, is one of the most important skills a software developer needs. If you can debug effectively, you&amp;rsquo;ll catch problems faster and even gain a better understanding of how things work under the hood.&lt;/p&gt;&#xA;&lt;p&gt;In frontend development, we have a variety of tools available to debug our code. We can use a &lt;a href=&#34;https://code.visualstudio.com/Docs/editor/debugging&#34;&gt;debugger&lt;/a&gt; to step through our code, we can log values to the browser console and we can use the &lt;a href=&#34;https://developer.chrome.com/docs/devtools/&#34;&gt;DevTools&lt;/a&gt; of our browser.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
