<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>web specs (summary) — farre's blog</title>
    <link>https://blog.farre.se/tags/web%20specs</link>
    <description>Post summaries tagged "web specs" on farre's blog</description>
    <atom:link href="https://blog.farre.se/rss/web%20specs-summary.xml" rel="self" type="application/rss+xml" />
    
    
    <item>
      <title>Tracing algorithms through web specifications</title>
      <link>https://blog.farre.se/posts/2026/08/17/tracing-web-specs/</link>
      <guid isPermaLink="true">https://blog.farre.se/posts/2026/08/17/tracing-web-specs/</guid>
      <pubDate>Mon, 17 Aug 2026 00:00:00 +0000</pubDate>
      <description>&lt;p&gt;A bug comes in, or someone shows me a page doing something surprising, and the question is always the same one. Is that what the spec says? Not what we all assume it says, and not what Gecko happens to do, but what the algorithm actually does when you follow it step by step. So I open &lt;a href=&quot;https://html.spec.whatwg.org/&quot;&gt;html.spec.whatwg.org&lt;/a&gt;, find the entry point, and start reading. Twenty tabs later I have usually lost the thread.&lt;/p&gt;

 &lt;p&gt;&lt;a href=&quot;https://blog.farre.se/posts/2026/08/17/tracing-web-specs/&quot;&gt;Read more&amp;hellip;&lt;/a&gt;&lt;/p&gt;</description>
    </item>
    
  </channel>
</rss>
