<story><title>WebKit Quirks</title><url>https://github.com/WebKit/WebKit/blob/main/Source/WebCore/page/Quirks.cpp</url></story><parent_chain></parent_chain><comment><author>tholman</author><text>If I&amp;#x27;m understanding L958+ [1] There&amp;#x27;s a hyper specific css class browser quirk because the login button for gizmodo&amp;#x2F;kotaku&amp;#x2F;etc&amp;#x27;s CMS&amp;#x27;s svg icon click event wasn&amp;#x27;t firing... and here I am fixing my day-to-day browser bugs like a chump&lt;p&gt;[1] &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;github.com&amp;#x2F;WebKit&amp;#x2F;WebKit&amp;#x2F;blob&amp;#x2F;main&amp;#x2F;Source&amp;#x2F;WebCore&amp;#x2F;page&amp;#x2F;Quirks.cpp#L958&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;github.com&amp;#x2F;WebKit&amp;#x2F;WebKit&amp;#x2F;blob&amp;#x2F;main&amp;#x2F;Source&amp;#x2F;WebCore&amp;#x2F;pa...&lt;/a&gt;</text></comment>
<story><title>WebKit Quirks</title><url>https://github.com/WebKit/WebKit/blob/main/Source/WebCore/page/Quirks.cpp</url></story><parent_chain></parent_chain><comment><author>matsemann</author><text>&lt;p&gt;&lt;pre&gt;&lt;code&gt;    shouldBypassBackForwardCache()
    &amp;#x2F;&amp;#x2F; Google Docs used to bypass the back&amp;#x2F;forward cache by serving &amp;quot;Cache-Control: no-store&amp;quot; over HTTPS.
    &amp;#x2F;&amp;#x2F; We started caching such content in r250437 but the Google Docs index page unfortunately is not currently compatible
    &amp;#x2F;&amp;#x2F; because it puts an overlay (with class &amp;quot;docs-homescreen-freeze-el-full&amp;quot;) over the page when navigating away and fails
    &amp;#x2F;&amp;#x2F; to remove it when coming back from the back&amp;#x2F;forward cache
&lt;/code&gt;&lt;/pre&gt;
Millions of pages have this bug, because of Safari&amp;#x27;s broken navigation. Nice that the big players get the browser to fix it for them. For instance, a common issue is you click a button that becomes disabled and shows a spinner while working, before forwarding to a new page. If you click back from the new page, Safari will render the previous page &lt;i&gt;exactly&lt;/i&gt; as it was when leaving, so in a broken loading state (instead of starting it from scratch).</text></comment>