<?xml version="1.0" encoding="utf-8"?>
<oembed>
  <version>1</version>
  <type>rich</type>
  <provider_name>Libsyn</provider_name>
  <provider_url>https://www.libsyn.com</provider_url>
  <height>90</height>
  <width>600</width>
  <title>75: Why isn't my custom property the value I expect?</title>
  <description>In this episode, Una and Adam discuss common gotchas with custom properties, which often feel fully reactive during use, but their limits and implementation details can popup at unexpected times and create a headache. They'll cover these situations and their solutions! &amp;amp;nbsp; Links: Value stages → https://goo.gle/3FDo7yA&amp;amp;nbsp; How custom property values are computed →https://goo.gle/49cOUiQ&amp;amp;nbsp; A complete guide to custom properties → https://goo.gle/40gtVb8&amp;amp;nbsp; The big gotcha with custom properties → https://goo.gle/45VwUHe&amp;amp;nbsp;&amp;amp;nbsp; CodePen → https://goo.gle/3SdMnyY&amp;amp;nbsp;&amp;amp;nbsp; &amp;amp;nbsp; Una Kravets (co-host) Twitter | Instagram | YouTube Making the web more colorful ✨🎨&amp;amp;nbsp; Web DevRel @googlechrome Unicorn face host of @toolsday &amp;amp;amp;  Designing in the Browser 🎬&amp;amp;nbsp; &amp;amp;nbsp; Adam Argyle (co-host) Twitter | Instagram | YouTube @GoogleChrome CSS DevRel; @CSSWG; VisBug maker; punk; CSS/JS/UX addict; 💀🤘 &amp;amp;nbsp; Catch more episodes → https://goo.gle/CSSpodcast&amp;amp;nbsp; Subscribe to Chrome for Developers → https://goo.gle/ChromeDevs </description>
  <author_name>The CSS Podcast</author_name>
  <author_url>https://thecsspodcast.libsyn.com</author_url>
  <html>&lt;iframe title="Libsyn Player" style="border: none" src="//html5-player.libsyn.com/embed/episode/id/28443572/height/90/theme/custom/thumbnail/yes/direction/forward/render-playlist/no/custom-color/88AA3C/" height="90" width="600" scrolling="no"  allowfullscreen webkitallowfullscreen mozallowfullscreen oallowfullscreen msallowfullscreen&gt;&lt;/iframe&gt;</html>
  <thumbnail_url>https://assets.libsyn.com/secure/content/194153620</thumbnail_url>
</oembed>
