Re: [w3c/IndexedDB] How should IDB connections and outstanding IDB transactions behave when a page enters back/forward cache? (Issue #381) from Sihui on 2024-08-15 (public-webapps-github@w3.org from August 2024)

From: Sihui <notifications@github.com>
Date: Wed, 14 Aug 2024 17:21:45 -0700
To: w3c/IndexedDB <IndexedDB@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <w3c/IndexedDB/issues/381/2290126404@github.com>

Hi @inexorabletash @lozy219, could you explain why a page must be evicted from cache? Can't the cached page just aborts  existing IDB activities when it might block other pages? 

The existing wpt test asserts page is evicted from cache and WebKit currently fails the check, but I don't see the eviction behavior specified anywhere. And from discussion above, it seems all we want to make sure it active page is not blocked on cached page, so I proposed a test change here: https://github.com/web-platform-tests/wpt/pull/47582. I verified it works in Chrome, Firefox and Safari. Please let me know if you have any concern.

-- 
Reply to this email directly or view it on GitHub:
https://github.com/w3c/IndexedDB/issues/381#issuecomment-2290126404
You are receiving this because you are subscribed to this thread.

Message ID: <w3c/IndexedDB/issues/381/2290126404@github.com>

Received on Thursday, 15 August 2024 00:21:49 UTC