<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>jake diagram (summary) — farre's blog</title>
    <link>https://blog.farre.se/tags/jake%20diagram</link>
    <description>Post summaries tagged "jake diagram" on farre's blog</description>
    <atom:link href="https://blog.farre.se/rss/jake%20diagram-summary.xml" rel="self" type="application/rss+xml" />
    
    
    <item>
      <title>Session History Diagrams in Firefox DevTools</title>
      <link>https://blog.farre.se/posts/2026/06/01/session-history-diagrams/</link>
      <guid isPermaLink="true">https://blog.farre.se/posts/2026/06/01/session-history-diagrams/</guid>
      <pubDate>Mon, 01 Jun 2026 00:00:00 +0000</pubDate>
      <description>&lt;p&gt;I’ve spent a lot of time at Mozilla working on session history, the machinery that keeps track of where you’ve been so the back and forward buttons do something sensible. It’s one of those parts of the browser that sounds simple from the outside and turns out to be anything but. Once you add iframes, nested iframes, and the subtle rules about when a navigation creates a new entry versus replacing the current one, the state you’re reasoning about gets large and hard to hold in your head.&lt;/p&gt;

 &lt;p&gt;&lt;a href=&quot;https://blog.farre.se/posts/2026/06/01/session-history-diagrams/&quot;&gt;Read more&amp;hellip;&lt;/a&gt;&lt;/p&gt;</description>
    </item>
    
  </channel>
</rss>
